Skip to main content
You talk to a team in its chat. The team’s leader answers you, or splits the work into tasks for teammates, and every task is a card on the Board. Teammates send their results back to the leader, who replies with the combined answer. This page follows one message through that loop, then explains the two ways Clawboo runs agents.

The pieces

  • The Clawboo server is one program that runs in the background on your computer. It runs your teams’ work, so closing the browser tab does not stop it. It keeps teams, chats, tasks and memory in a database in your Clawboo folder (~/.clawboo by default).
  • The dashboard is the page you use in your browser. It talks only to that server.
  • Runtimes are the programs that run agents: Clawboo Native (built in), Claude Code, Codex, Hermes and the OpenClaw Gateway. See Choose a runtime.
  • Providers are the AI services your agents’ prompts go to, such as Anthropic, OpenAI or a local Ollama.
Prompts go only to the providers and apps you connect. There is no Clawboo account, and Clawboo itself sends no telemetry.

What happens when you send a message

1

You post in a team's chat

Write in General or in a room. To aim the message at one agent, start it with @ and the agent’s name.
2

Clawboo picks who answers

The agent you mentioned answers. Otherwise Boo Zero, your team leader, does. With no Boo Zero, the team’s Leader answers if it is in this chat, and otherwise the chat’s first member.
3

The turn runs on the server

The turn runs on that agent’s runtime. You can close the tab; the chat catches up when you come back.
4

It answers, or hands off work

A quick question gets a direct answer. For work with several parts, the leader hands pieces to teammates, and each hand-off becomes a task on the Board, assigned to that teammate. Each runtime signals a hand-off its own way, and Clawboo reads all of them.
5

Teammates do their tasks

Teammates work at the same time. A busy teammate finishes its current task first, and the new one waits in To do. A teammate can hand part of its own task to someone else.
6

Results come back

As tasks finish, their results go back to whoever handed out the work, in one batch. Each result also lands on its task card. Clawboo tells the leader which tasks are still out.
7

The leader answers you

The leader combines the results into one reply in the chat. You should see that reply, and the task cards in Done.
What each agent is told on every turn is listed in What an agent sees.

What you see while it works

  • In the chat, the reply streams in, and each hand-off appears as a task card with its status, such as Queued, Working or Done.
  • On the Board and in the chat’s Tasks card, cards move from To do to In progress to Done. Anything that waits on you collects under Needs you.
  • The Team graph shows which agents are working.
  • The Activity card shows each tool call as it happens.
The Board in Week view: Needs you holds a blocked task and two unassigned ones with Assign to and Dismiss, In progress holds running and Verifying cards, Done holds finished tasks, and two scheduled Routine runs sit in To do

How it ends

  • The answer arrives in the chat.
  • You press Stop. While agents in a chat are working, the send button turns into Stop. It ends every run in that chat, and their tasks go back to To do, where they do not restart on their own. Your other chats keep going.
  • Something fails, or something needs you: see the next section.

When something goes wrong

Troubleshooting lists the messages you may see and what to do about each.

Two ways Clawboo runs agents

Everything above runs on Clawboo’s team chat path. A second path, the task runner, runs one board task at a time, for agent Routines and for runs started through the API. The two paths do not give an agent the same things: An agent Routine you create in the app sends only its instructions, so it runs on the task runner without a repository: no worktree and no checks, but with memory added and circuit breakers on. A team Routine posts its instructions into the team’s chat, like a message from you. Several rows have their own page: What agents can do covers where agents work, How work is checked covers checks, and Budgets and guardrails covers budgets and breakers.

OpenClaw and one-to-one chat

  • OpenClaw agents never use the task runner. In team chat they run over the Clawboo server’s own connection to the OpenClaw Gateway, so they keep working with the tab closed. An OpenClaw agent Routine goes through a separate dispatcher, with no worktree, no checks and no circuit breakers, and it is stopped after 10 minutes by default.
  • A one-to-one chat on an agent’s page is a plain conversation, outside both paths. A Clawboo Native, Claude Code, Codex or Hermes agent’s chat runs on the server and starts in the agent’s team folder. An OpenClaw agent’s chat goes over the Gateway connection your browser holds.
  • Boo Zero’s own chat is the exception on the server: a hand-off in its reply starts on that team’s board, through the team chat path, and the result comes back to the chat. An OpenClaw Boo Zero’s chat cannot do this, because the server never sees its reply. See Boo Zero.

The team’s own limits

Team chat has no circuit breakers, but it has limits of its own:
  • One turn can hand off at most 8 tasks. Extra hand-offs are dropped with a note.
  • Hand-offs go at most three levels below the leader. The agent on a third-level task must do the work itself.
  • Clawboo stops handing a task to a teammate that has failed it 3 times in a row.
  • A teammate that goes quiet for 8 minutes is stopped (24 minutes while inside one tool call). Time the computer spends asleep does not count.
Limits and defaults lists every number.
  • One server. The clawboo command starts a server that serves the dashboard and the /api/* routes on one port, the first free one from 18790. It listens on 127.0.0.1 unless you set HOST. CLI covers ports and stopping the server, and Security covers the access token.
  • Two engines. Team chat runs on one team engine per chat room (teamOrchestrator.ts and serverDeliver.ts in apps/web/server/lib/teamChat/). The task runner is runTaskOnRuntime in apps/web/server/lib/executorRunner.ts; see Executor runner.
  • Hand-off signals. A Clawboo Native leader calls its delegate tool. A Claude Code, Codex or Hermes leader calls the team_delegate tool. An OpenClaw agent writes a <delegate to="@Name"> block, or uses sessions_send. A <plan> block sets up an ordered chain of steps. Delegation and orchestration has the details.
  • Clawboo’s tools. Every runtime reaches Clawboo’s Tasks, Memory and Tools MCP servers, and every runtime except OpenClaw also gets TeamChat. See MCP servers.
  • Where agents are stored. OpenClaw agents are mirrored from the Gateway. Other agents exist only in Clawboo’s database.
  • The event log. Each step is recorded in an event log that feeds the Activity cards, the Observability panel and the live status on a team’s graph. A graph’s layout comes from the team’s members and each agent’s routing, not from the log.
  • Other traffic. Besides your providers and connected apps, Clawboo contacts GitHub for the marketplace catalog and npm to check for updates.
Last modified on November 14, 2026