Adding another agent

A second agent takes about five minutes of setup, because your computer is already set up. Step by step, no coding needed.

Your first agent took a while: installing tools, the plugin, its packages. None of that happens again. A new agent needs only three things: a folder of its own, the plugin switched on in that folder, and a name.

Each agent has its own memory, tasks, and personality. Nothing one agent learns shows up in another. A common setup:

Agent	Folder	Job
Kevin	`~/Documents/Agents/Kevin`	Personal life, family, side projects
Scout	`~/Documents/Agents/Scout`	Client work

The examples below add Scout. Swap in your own name wherever you see it.

What you can skip

Step from your first install	Again?
Prerequisites: Homebrew, Claude Code, Bun, uv, helpers	No, they're per computer
Logging in to Claude Code	No, unless this agent should bill a different account (see below)
Adding the marketplace (`/plugin marketplace add`)	No, your computer remembers it
Installing the plugin's packages (`bun install`)	No, every agent shares them
Creating a folder, switching the plugin on there, running `init`	Yes, that's this page

Pick a name

Give every agent a different name and a different emoji. The name is how the agent introduces itself, and it appears in the session banner, on the dashboard, and in reports. The emoji signs its briefings and standups. With two agents both called Kevin, you can't tell at a glance which one you're talking to.

Use letters, numbers, spaces, or hyphens: Scout, Sage, Acme Assistant.
Name the folder after the agent, so Scout lives in ~/Documents/Agents/Scout. The folder is what keeps the agents apart, so a matching name avoids mix-ups later.
Pick an emoji that isn't 🍌, which is Kevin's default.

More on how names work: Naming your agent.

Set it up

Create the agent's folder

Open a new terminal window and run:

mkdir -p ~/Documents/Agents/Scout && cd ~/Documents/Agents/Scout

Start the new folder empty. Don't copy your first agent's folder: that copies its memory, name, and history too. To start from your first agent's personality and setup instead, see Start from your first agent.

Switch the plugin on in this folder

In the same terminal, start Claude Code:

claude

It asks "Do you trust the files in this folder?". Answer Yes: saying no quietly turns the plugin off. You're already logged in, so no browser opens.

Then type:

/plugin install agent-kevin --marketplace AgentLayer1/agentlayer-agent-marketplace

It opens the plugin's details: choose the project scope, which switches it on for this folder only. Then type /exit.

Running the plugin from your own fork? Use /plugin install agent-kevin@agentdev-kevin instead, and choose Install for all collaborators on this repository (project scope) when it shows the plugin's details.

Start again and run the setup wizard

claude

Then type:

/agent-kevin:init

The wizard checks your computer, finds everything already in place, and starts asking questions.

Give it its own name

The first question is "What should this agent be called?", and the suggested answer is Kevin. Don't take it: choose Something else and type the new name, Scout.

Because the name is new, the wizard then asks for an emoji (pick a different one from your other agents) and an avatar (an image file or link, or skip).

Answer the rest for this agent's job rather than your first agent's: its role, the company it works for, the projects it handles, the code it can reach. Every question after the name can be skipped and filled in later.

Restart the agent

When the wizard finishes, type /exit, then start it again from its folder:

cd ~/Documents/Agents/Scout && claude

If it asks you to trust the marketplace, accept. Your new agent greets you by its new name.

Using Codex too?

Create the agent with Claude Code as above, and answer Yes when the wizard asks whether you also run Codex from this home. Then run codex from the agent's folder and $upgrade once. Details on the Codex page.

Its own bill

Out of the box, every agent uses the Claude account you're logged into, so all their usage counts against one plan. To give an agent its own account, for example a work account for a client agent, follow Billing per agent. It takes about ten minutes, and from then on you start that agent with agent instead of claude.

Switching between agents

You pick the agent by the folder you start it from. Open one terminal tab per agent:

cd ~/Documents/Agents/Kevin && claude

cd ~/Documents/Agents/Scout && claude

Both can run at the same time. Each one only ever reads and writes its own folder, so their memories never mix, even when they work on the same code. An agent on its own bill starts with agent in place of claude.

If you use Obsidian, open each agent's folder as its own vault.

Start from your first agent

Want Scout to begin with Kevin's personality, rules, and skill setup, without Kevin's personal memory? Make a seed bundle from Kevin first: in Kevin's session, ask it to "make a seed bundle" (the seed skill). It walks you through what to include and makes a zip. Then hand that zip to Scout's wizard when it asks "Starting from a teammate's seed bundle?". See Seed bundles.

Good to know

Each agent has its own settings. Keys and add-ons (SEO, GitHub, databases) are set up per agent. Run the configure-skills skill in each agent that needs them.
Updating the plugin. Pull the new version once, then run the upgrade skill in each agent, since each folder has its own files to bring up to date. See Updating.
Start agents from their folder only. A session started anywhere else loads no agent and remembers nothing.

If something's off

What you see	What to do
`/agent-kevin:init` isn't recognized	The plugin isn't on in this folder yet, or Claude Code wasn't restarted. Redo step 2, then step 3
The wizard says the folder is already set up	You're in another agent's folder. Type `/exit` and check the folder you started from
The wizard says the folder looks like a code project	You started in a code folder. Pick the suggested option, which tells you the exact line to start from the right folder
The new agent calls itself Kevin	The name question took the default. Type `/agent-kevin:rename-agent` to rename it everywhere
Usage from both agents lands on one account	Expected out of the box. See Billing per agent