Skip to main content
Every agent on a team has its own runtime, the engine that does its thinking and acting. One team can mix them: a Claude Code agent fixes a bug, a Codex agent reviews the fix, and a Clawboo Native agent writes the changelog, while Boo Zero leads all three. Use this recipe when two or more runtimes are connected and you want each member on the one that suits its job. What you’ll build: the built-in Dev Team (Bug Fixer Boo, Code Reviewer Boo and Doc Writer Boo) with each member on a different runtime. Time: about 15 minutes, plus the time to install any runtime you don’t have yet.

Before you begin

Clawboo is installed and onboarding is done. At least two runtimes must read Connected in Settings > Runtimes. Each one needs: For the click path per runtime, see Providers and runtimes.

Steps

1

Connect the runtimes you want

Open Settings (Cmd/Ctrl + ,) and click Runtimes under Workspace. On each runtime’s row, use its button: Install, Connect, Sign in, or Set up for OpenClaw.You should see two or more rows read Connected. Claude Code reads Needs key until an Anthropic API key is connected; a signed-in claude CLI on its own does not count.
2

Start the deploy

In the sidebar, click Marketplace. On the Teams tab, find Dev Team and click Deploy. Customize team opens.
3

Pick a runtime for each member

Under Teammate colors, each member’s row has a runtime menu with Clawboo Native, OpenClaw, Claude Code, Codex and Hermes. For example:
  • Bug Fixer Boo: Claude Code
  • Code Reviewer Boo: Codex
  • Doc Writer Boo: Clawboo Native
A runtime that is not connected shows Connect → in the menu. Choosing it closes this dialog and opens Settings > Runtimes (for OpenClaw, its setup), so connect first and then deploy. Clawboo Native, OpenClaw and Hermes members also get a model menu. Claude Code and Codex members run on their own default model.
4

Deploy the team

Click Deploy team.You should see Team deployed!, and then the team’s General chat opens. A member keeps the runtime it was deployed on; the dashboard cannot change it later.
5

Meet the team and hand it work

On the Meet your team card, click Get Started, introduce yourself, and click Continue to team chat. Then ask for work that needs each member, for example:
Boo Zero splits the request into tasks. Each task runs on its teammate’s own runtime, and all of them land on the same board and in the same Tasks card.
In team chat, Claude Code and Codex run with their own approval prompts turned off, and Hermes asks only before the commands its own policy flags. On a task they start in the task’s own folder inside the team’s folder (~/clawboo-work/teams/<team id>/tasks/<task id>), and otherwise in the team’s folder (~/clawboo-work/teams/<team id>). Either way they can still read and change any file your user account can. There is no isolated checkout on this path. Point them only at work you have committed or backed up, and read What agents can do. For a separate git checkout per task, see Hand a task from one runtime to another.

Check that it worked

  • On the Team graph card beside the chat, each Boo carries a small badge for its runtime.
  • In the Tasks card, a finished task’s detail names the runtime that ran it.
  • The tasks of all three members appear on the same Board.

What each runtime brings

The runtime overview compares them in full, and Budgets and spend explains estimated costs.

How memory differs

Clawboo keeps one shared memory, and every team member uses it through memory tools. What a member sees depends on its runtime: In team chat, agents look things up in memory when they decide to. Clawboo adds relevant facts to an agent’s prompt by itself only for task runs started through the REST API or an agent routine. See Memory.

Who leads a mixed team

Boo Zero leads every team, whatever runtimes the members use. After an onboarding with only a ChatGPT sign-in, Boo Zero is the first Codex agent that onboarding created. Otherwise it is a Clawboo Native agent once any team has a Clawboo Native member and a native provider is connected, and the OpenClaw Gateway’s default agent until then. See Boo Zero.

Variations

Troubleshooting

What it means: that runtime is not connected yet.Fix: close the dialog, connect the runtime in Settings > Runtimes until it reads Connected, then deploy the team again.
What it means: Claude Code needs an Anthropic API key before it reads Connected. A signed-in claude CLI does not count.Fix: connect an Anthropic API key on the Claude Code row in Settings > Runtimes. See Claude Code.
What it means: at least one member is set to OpenClaw, and no OpenClaw Gateway is connected.Fix: set those members to another runtime, or set up OpenClaw first. See OpenClaw.
What it means: no member could be created on its runtime. The new team stays, empty.Fix: check each member’s runtime in Settings > Runtimes. Then close the dialog, delete the empty team (right-click its icon in the team rail and choose Delete team only), and deploy from the Marketplace again. If only some members fail, a message lists them, for example “2 of 3 agents created”.
What it means: OpenClaw agents read and save global facts only.Fix: add the facts it needs under Memory in the sidebar. Facts you add there are global, so every agent can read them. Or give the work to a member on another runtime.
What it means: each Hermes agent’s memory lives in a Hermes profile named after the agent’s id. An agent you deploy again is a new agent with a new, empty profile.Fix: keep the original agent. Deleting it and deploying again starts its memory from scratch.

Next steps

Last modified on November 14, 2026