Before you begin
A team template creates real agents, so you need at least one runtime that can run them:- Clawboo Native, the built-in runtime, with a provider: an API key or a local Ollama.
- Or the OpenClaw Gateway, Claude Code, Codex or Hermes.
Create a team
1
Open the team templates
In the team rail, click the dashed + at the end of the team icons (Create a team). The Marketplace opens on its Teams tab.
2
Pick a starting point
Click Deploy on a team card to start from that template. To see who is on a team first, click Details. For an empty team, click the Start from scratch card.
3
Customize the team
Set the team’s name, badge and colors, and each member’s runtime and model. See Customize the team.
4
Deploy
Click Deploy team, or Create team for an empty team. Clawboo creates each agent and shows its progress.You land in the new team’s General chat. Before you can message the team, a Meet your team card asks you to introduce yourself. See Team chat.
Customize the team
The customize step has three sections.Choose a runtime and model for each member
The roster under Teammate colors lists each member. Each row has:- A runtime picker: Clawboo Native, OpenClaw, Claude Code, Codex or Hermes. One team can mix runtimes.
- A model picker, for members on Clawboo Native, OpenClaw or Hermes. Pick a provider first (only the providers you connected are listed), then a model. Until you pick one, it reads Default, followed by the model the member will run on Clawboo Native and OpenClaw.
- A Marketplace template suggests OpenClaw for every member. A team from scratch suggests Clawboo Native. During first-time setup, every member starts on the runtime you connected in setup.
- When the suggested runtime is not connected, the row starts on the first runtime that is, in this order: Clawboo Native (with an API key or a local Ollama), OpenClaw, Claude Code, Codex, Hermes. The row says so, for example OpenClaw unavailable · using Codex when you only signed in with ChatGPT. With nothing connected, the row stays on Clawboo Native.
- You can pick OpenClaw only while the OpenClaw Gateway is connected, and Claude Code, Codex or Hermes only once you have connected them. Clicking a greyed-out runtime closes this dialog and opens Settings > Runtimes so you can connect it.
What happens when you deploy
- Clashing names get a number. If agents or a team with the same names already exist, Clawboo gives the new ones the next free number, for example Code Reviewer Boo 2. It also updates who hands work to whom to match.
- One failed agent does not stop the rest. Clawboo keeps going, then lists any failures in a message such as 2 of 3 agents created (Writer Boo failed). If no agent can be created, you return to the customize step with No agents could be created. Check that the runtime is connected, then retry. Clawboo removes the empty team it made, so you can click Deploy team again. If it cannot, the message says so: delete that team from the team rail, or the next try adds a second team.
- OpenClaw members need the Gateway. If you put a member on OpenClaw while the Gateway is offline, the deploy stops with Connect an OpenClaw Gateway to deploy the OpenClaw members, or switch them to another runtime.
- The team gets a brief. Clawboo writes a starting team brief that you can edit.
The team’s Leader
When you deploy a template, a member whose name or role reads as a lead (CTO, Team Lead, Project Manager, Coordinator and similar) gets a Leader badge in the roster. That member becomes the team’s Leader.- Boo Zero still leads the team. On the team graph, the Leader sits between Boo Zero and the other members.
- On Clawboo Native, the Leader gets the team-lead instructions and the leader model. The other members get the specialist ones.
- When your install has no Boo Zero, the Leader leads the team’s chats. A team with no Leader is led by its first member.
Brief and rules
Open a team’s settings from any of its chats: in General or a room, click the gear in the chat header. Its tooltip is the team’s name followed by brief & rules. The settings window has six sections: Icon, Accent color, Color collection, Brief, Rules and Work check. Icon and color changes save as you make them.
Team rules
Team rules are instructions that every member of the team follows. Clawboo adds them to every turn in the team’s chats (General and every room), for Boo Zero and for each teammate, including the work Boo Zero hands out. A correction you save as a rule keeps applying, so you do not have to repeat it. Rules apply from the next turn. A team Routine posts into General, so its runs follow the rules too. A Routine aimed at one agent runs without them. You can add rules in two ways.- The Rules box
- /rule in a chat
In the team’s settings, type in Rules, one rule per line, then click Save rules. You should see Team rules saved. Rules can be up to 4,000 characters; a longer save fails with Could not save rules.
/rule keeps your rules as a bulleted list: it turns every line into a bullet, drops blank lines, and skips a rule that is already there (ignoring capital letters). It works only with a space and some text after it, so /rules or /rule: is sent as a normal message. If the new rule would take the rules past 4,000 characters, you see Could not save team rule. Try again?
Team brief
The brief describes the team: what it is for, who is on it, and how they work together. Clawboo writes one when you deploy a template, and you can edit it in the team’s settings. Regenerate rebuilds it from the current members; nothing changes until you click Save. Boo Zero reads a team’s brief only when you start a message in Boo Zero’s own chat with @ and the team’s name, and then only its first 900 characters. Team chats do not include the brief, so use rules for anything the team must follow. See What Boo Zero reads.Work check
The work check is the command Clawboo runs to check an agent’s work on the team’s tasks, such asnpm test. It checks two kinds of task, and a checked task reaches Done only if the command succeeds:
- Team chat work: a task handed out in team chat, or one you give an agent on the Board, that changed the team’s folder. The task’s own folder sits inside the team’s folder, so a change there counts. Clawboo runs the command in the team’s folder after the agent’s run ends. Without a work check, this work is not checked. OpenClaw agents work outside the team’s folder and are not checked. If Clawboo cannot record the folder when a task starts, that task is not checked, and a comment on it says so.
- Task-runner tasks that changed files in their own git worktree. Clawboo runs the command in the task’s worktree.
&& between them instead. If a save fails, you see Could not save the work check. and your edit stays in the box.
Above the box, Active check says which check runs now. It reads the team’s command again when you come back to the window, so it also shows a change made elsewhere, for example through the API:
- The command, set for the team: every check of the team’s tasks runs it from the next check on, and each new task worktree starts with it. The task’s Verification section shows it as set for the team. An agent cannot change it by editing its own files.
- Each agent’s own, written by the agent in its task worktree: no work check is set, so each agent writes its own check in its task worktree’s
init.sh, and the task shows it as written by the agent. An agent that writes no check fails the check. This applies only to task-runner tasks; team chat work goes unchecked.
Rename a team
The dashboard has no rename control for a team: you name it on the customize step. To rename a team later, use the API call under Under the hood at the end of this page.Refresh a team’s protocol
Each member’s AGENTS.md lists the team and how to hand work to teammates. After you add or remove members, right-click the team’s icon in the team rail and choose Refresh Protocol. Clawboo rebuilds that file for every member and keeps each member’s routing rules. Refresh Protocol needs the OpenClaw Gateway connected, even for a team with no OpenClaw members. Without it you see Not connected to Gateway. Only OpenClaw agents read AGENTS.md as instructions; on every runtime it also draws the team graph’s links (see Agents).Archive a team
Right-click the team’s icon in the team rail and choose Archive. The team leaves the list of teams for the rail’s Archived group, which also puts its chats and its Home out of reach. Nothing is deleted: its agents, chats, tasks and the files in its team folder, task folders included, stay in Clawboo. To bring a team back:- At the end of the team icons, click Archived (an archive icon with the number of archived teams). It appears only while a team is archived.
- The archived teams show dimmed, each named with (archived) after it. Click the team, or right-click it.
- Choose Unarchive. The team returns to the team rail.
Delete a team
Right-click the team’s icon in the team rail and choose how much to delete.
Both choices also delete the team’s rules, its brief, its rooms and your introduction to the team, and the team’s folder (
~/clawboo-work/teams/<team id>) with every file its agents saved there, including each task’s folder under tasks/, and the link to it that an older version’s ~/.clawboo/workspaces/<team id> may hold. The confirmation says so: “The team’s folder and the files its agents saved there are deleted too.” If the folder cannot be removed, the team is still deleted, and a message says its team folder could not be removed.
Both choices stop whatever the team is doing first. Its runs end, a person’s request still open on its board is cancelled with the work under it, and its other tasks stay on the board, where nothing can start them again. A result still on its way to one of its agents is dropped. The result stays on its task.
Its routines go different ways. An agent routine goes with its agent: with Delete team only it keeps its schedule and files its tasks with no team, in the shared _no-team folder, unless it runs one of the tasks the team left behind, and then its next run fails and stops it. With Delete with agents it is deleted with its agent. A team routine stays, and its next run fails with The team this routine posts to no longer exists., which stops it until you delete it or point it at another team.
Delete with agents works without the OpenClaw Gateway. An OpenClaw member leaves the Gateway at once if it is connected, otherwise the next time Clawboo connects to it. If some agents cannot be deleted, the team is still deleted, and a message says how many agents were removed.
Troubleshooting
Connect an OpenClaw Gateway to deploy the OpenClaw members
Connect an OpenClaw Gateway to deploy the OpenClaw members
What it means: you put a member on OpenClaw while the OpenClaw Gateway is offline.Fix: connect the Gateway in Settings > Runtimes, or switch those members to another runtime on the customize step.
No agents could be created
No agents could be created
What it means: no agent in the template could be created. Clawboo removes the empty team it made for this deploy.Fix: open Settings > Runtimes, check that the runtimes you picked are connected, then deploy again. If Clawboo could not remove the empty team, the message says so and the team stays in the team rail. Delete it there, or the next deploy adds a second team.
The new agents have a number after their names
The new agents have a number after their names
This is expected. A team or agents with the same names already exist, so Clawboo numbered the new ones to keep every name unique.
Refresh Protocol says Not connected to Gateway
Refresh Protocol says Not connected to Gateway
Refresh Protocol needs the OpenClaw Gateway connected, even for a team with no OpenClaw members. Connect it in Settings > Runtimes, then try again.
A team disappeared from the team rail
A team disappeared from the team rail
The team was archived. Its agents, chats and tasks are still in Clawboo. Click Archived at the end of the team icons, click the team, and choose Unarchive. See Archive a team.
The team does not follow a rule
The team does not follow a rule
Rules apply from the next turn in the team’s chats, not to replies already sent. Open the team’s settings and check that the rule is in Rules. A Routine aimed at one agent runs without the team’s rules; a team Routine follows them.
Under the hood
Under the hood
- Files a deploy writes. Each member gets a SOUL.md (its persona plus the default House Style personality), an IDENTITY.md, and an AGENTS.md that lists the teammates and how to hand them work. On an OpenClaw member, AGENTS.md also carries the catalog’s tool notes. Which runtime reads which file is on Agents.
- OpenClaw config. If any member’s routing names a teammate, Clawboo turns on agent-to-agent messaging in the OpenClaw Gateway’s config.
- API calls.
PATCH /api/teams/:idrenames a team or changes its Leader. It takes any ofname,icon,color,colorCollectionId,leaderAgentId(an agent id, ornullfor no Leader) andisArchived. Archive and Unarchive in the team rail sendisArchivedthrough this same call.
Next steps
- Team chat: talk to your team, add rooms, and introduce yourself.
- Agents: change one member’s model, personality or files, or move it to another team.
- Boo Zero: how your team leader is chosen and what it reads.
- Marketplace: find more teams and agents to deploy.
- Teams API reference: every team route and field.