Multiple agents
One plugin install, several homes. Personal, work, and specialist agents that never share a brain.
Several homes, one plugin
~/Documents/Agents/Kevin/ # personal projects, journals, life ops
~/Documents/Agents/Scout/ # client work, professional persona
~/Documents/Agents/Sage/ # SEO-focused, only the SEO pack configuredThe plugin code lives once on disk; each home is independent. Switch by launching from the one you want. The home is resolved from where you launched, so nothing needs configuring to keep them apart. Give each its own name with the rename-agent skill (see Naming); they still share the plugin's command namespace, which is plumbing you never see once each IDENTITY.md carries its own name.
The one rule
No KEVIN_* variable in a user-level settings file or your shell rc. It is machine-wide and outranks launch-directory resolution, so one value captures every session for one brain. Per-home config goes in that home's settings.local.json under the neutral AGENT_* names.
Under Claude Code each home can even bill against its own account. See Multiple accounts.
Augmenting an existing project
You already have a repo with its own AGENTS.md or CLAUDE.md and want Kevin's memory and task system layered on top.
Launch your host from the repo and run the init skill there. Init never touches a root CLAUDE.md (Kevin's Claude Code bridge is .claude/CLAUDE.md, and both load) and appends its manual to a pre-existing AGENTS.md rather than replacing it. Your project context and Kevin's identity coexist.
A team-shared agent
Drop Kevin into a team repo, commit the identity stack (AGENTS.md, SOUL.md, IDENTITY.md, .claude/, knowledge/), and gitignore settings.local.json. Every teammate gets the same agent identity and trusts the plugin once on their host.
For a teammate who should start from your agent but then diverge freely, use a seed bundle instead. A team with no agent yet can start every member from the same wizard bundle.
Keeping brains and code apart
Brains under ~/Documents/Agents/, code flat under ~/Developer/, never nested. The brain opens cleanly as an Obsidian vault, many brains can run against one code tree, and cloud sync never drags repos along. See Workstation for the full layout.
Seed bundles
Hand an agent's persona and setup to a teammate as a zip, or start one from the web wizard. Memory, sessions, and credentials stay the recipient's own.
The agent is the harness
Layer 02. The agent that loads the context every session, and the rails around the model that make it safe to use.