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
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.
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
Connect an OpenClaw Gateway to deploy the OpenClaw members, or switch them to another runtime.
Connect an OpenClaw Gateway to deploy the OpenClaw members, or switch them to another runtime.
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.
No agents could be created. Check that the runtime is connected, then retry.
No agents could be created. Check that the runtime is connected, then retry.
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”.
An OpenClaw member doesn't know what the team saved
An OpenClaw member doesn't know what the team saved
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.
A Hermes member forgot what it learned
A Hermes member forgot what it learned
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
- Choose a runtime: what each runtime supports, side by side.
- What agents can do: permissions per runtime, before you give coding agents real work.
- Hand a task from one runtime to another: pause a coding task on one runtime and finish it on another.
- Memory: browse and add the facts your team shares.
- Budgets and spend: which runtimes report real cost and which are estimated.