Onboarding
What the init wizard asks, what it writes, and the one convention every session depends on.
The wizard
Run the init skill from a fresh session in the home (/agent-kevin:init in Claude Code; under Codex, create the home from Claude Code for now).
❓ What should this agent be called? (default: Kevin; plus emoji + avatar if you rename)
❓ Its character (SOUL): accept default, or refine?
❓ Its role (IDENTITY): general / coding / research / planning / custom?
❓ Your name and home timezone?
❓ Paste any URLs about you (blog, LinkedIn, GitHub) so Kevin seeds your profile
❓ Paste a path or URL for your avatar (optional)
❓ Should knowledge/ and projects/ live somewhere else?
❓ Communication style and any hard preferences?
❓ Configure skill packs (SEO, Browser, third-party libraries)?
❓ Starting from a teammate's seed bundle? (applied after the scaffold)
❓ Do you also run Codex from this home?
❓ Confirm + scaffoldAbout five minutes. Each answer becomes the default for later steps, the name first of all, since every file the wizard writes is phrased in it. See Naming your agent. A seed bundle from a teammate or the web wizard answers most of it for you.
What it writes
| File | Role |
|---|---|
AGENTS.md | The operating manual. Harness-neutral: every AGENTS.md-aware CLI reads it |
SOUL.md / IDENTITY.md / USER.md | Kevin's character, Kevin's role, your headline |
knowledge/, projects/ | The brain and the work, optionally at custom locations |
.claude/CLAUDE.md | The Claude Code bridge: @-imports the manual and the identity stack |
.claude/settings.json | The home's permissions: marketplace registration plus grants for the always-on core tools. Read by Claude Code directly and by Codex through its generated wiring |
.claude/settings.local.json | Gitignored. Non-secret config only; secrets go in .kevin/secrets/.env |
.codex/ | Only when you said you run Codex: hooks, MCP registration, permission profile, rules. See Codex |
You fill secret values in your editor, never in chat. Neither init nor configure-skills asks for a key in conversation, because pasted secrets touch the transcript.
If you moved knowledge/ or projects/ outside the home, the wizard appends the needed permission entries so the host can reach them without prompting.
Exit and relaunch
Plugin registration only takes effect on a fresh session.
/exit
cd ~/Documents/Agents/Kevin && claudeWatch for a marketplace trust prompt on first relaunch and accept it. If you miss it, recover with /plugin marketplace add … and /plugin install agent-kevin@agentlayer.
The one convention
Always launch from the agent home, then reach your code from inside the session.
The plugin is enabled by the home's settings, so a host loads it only for sessions started there. That single fact gives you the identity stack, the skills, the MCP tools, and session capture. It is also what keeps several agents on one machine apart with no configuration.
Reaching your code. Add the repos you work in to permissions.additionalDirectories in the home's settings.local.json. Both hosts honour it: Claude Code grants file access there, and Codex lists the same paths as workspace roots.
{
"permissions": {
"additionalDirectories": ["/Users/you/Developer/acme", "/Users/you/Developer/side-project"]
}
}Set AGENT_CODE_PATH to your primary repo and its git activity shows up in every session's context.
The session can wander, the anchor cannot. Once running, cd anywhere. The home is resolved from the launch directory, which never moves, so capture lands in the right brain even when the shell has roamed three repos deep.
What you give up
A session started outside a home is not captured, and says nothing about it. No plugin loads, so no hooks run. Do not put a KEVIN_* variable in a user-level settings file to work around this: it is machine-wide and hands every session to one brain. Per-home config belongs in that home's settings.local.json.