Terms
A
Access token: an optional secret that guards the dashboard and Clawboo’s API. Without one, anything that can reach the server can use it. With one, each browser presents the token once before it gets in. Set one before you open Clawboo to other computers. See Security model. Agent: an AI worker on one of your teams. Each agent runs on one runtime and one model, follows its own instruction files, and appears in the dashboard as a Boo. See Agents. Agent files: the instruction files an agent keeps, edited under Details > Agent Files on its page. SOUL.md holds its personality and instructions, and AGENTS.md lists the teammates it hands work to. What each file does depends on the runtime. See Agents. Approval: a request that waits for your yes before it goes ahead: a shell command from a Clawboo Native or OpenClaw agent, a connector call that needs a yes, or a risky hand-off in team chat. Approvals appear in Needs you on the Board and in the chat where the agent works. See Approvals.B
Board: every task in one place, by status and by day. Its first column, Needs you, holds what waits on you. See Board. Boo: how the dashboard draws an agent: a small mascot with a badge for the agent’s runtime. Buttons such as Create Boo use the word too. See Agents. Boo Zero: your team leader. One agent leads the chats of every team: it answers messages that @mention no one, and hands work to teammates. Clawboo creates it on Clawboo Native once you have a Clawboo Native agent on a team and a connected provider; otherwise it uses your OpenClaw Gateway’s default agent. See Boo Zero. Brief: a team’s short description, edited together with its rules. Boo Zero reads it 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. Guidance Boo Zero must follow on every turn belongs in the team’s rules. See Teams and Boo Zero. Budget: a dollar limit on one agent, team or mission. In warn only mode, the default, Clawboo counts spend and warns you as the budget fills. In hard cap mode, which you opt into, it also pauses work at 100%: new runs are refused, though a run already going may finish first. No budget exists until you create one. See Budgets and spend.C
Capabilities: the skills, tools and connectors your agents can use. Settings > Capabilities lists them all, with what each one needs. See Capabilities. Circuit breaker: an automatic stop for a task-runner run that is going nowhere, such as one that repeats the same failing call. See Budgets and guardrails. Claude Code: Anthropic’s coding agent, one of the runtimes Clawboo can run agents on. It needs an Anthropic API key. See Claude Code. Clawboo Native: Clawboo’s built-in runtime, with nothing to install. It runs agents on an API key from one of ten providers (Anthropic, OpenAI, OpenRouter, Google, xAI, Groq, Mistral, Together, Cerebras or Moonshot), or on a local Ollama with no key. See Clawboo Native. Clear chat: empties one chat (General or a room) and starts that conversation fresh for its agents. Clawboo sets the messages aside rather than deleting them, and the chat’s tasks stay on the Board. See Team chat. Codex: OpenAI’s coding agent, one of the runtimes Clawboo can run agents on. You connect it with Sign in with ChatGPT, not an API key. See Codex. Connector: a link to an outside app or tool, such as GitHub, Gmail, a folder or a web browser, that agents use through Clawboo. Connecting one gives no agent access until you share it with that agent, under Who can use it? in the connector’s detail pane or on the graph. The two browser connectors are the exception: every new agent gets them. See Connectors. Cost estimate: a cost Clawboo works out itself when a runtime reports none, marked est. on task cards. Models Clawboo has no price for are estimated at a default rate. A model your own Ollama serves is not estimated: it costs nothing, so its runs read free. See Budgets and spend.D
Delegation: an agent handing part of its work to a teammate, also called a hand-off. Each hand-off becomes a task on the Board. See How a team works. Device pairing: OpenClaw makes you approve each new device before it can connect to the OpenClaw Gateway. Clawboo shows an Approve this device card that does it for you. See OpenClaw.F
Fleet: Settings > Insights > Fleet: all your agents at a glance, with recent task and check results, spend, and health per runtime. See Tour the dashboard.G
General: a team’s main chat, with every member, listed as General (Main Room). You can clear it, but not rename or delete it. See Team chat. Governance: Settings > Insights > Governance: budgets, limits, the approval queue and the audit log. See Budgets and guardrails.H
Hermes: an open-source agent from Nous Research, and one of the runtimes Clawboo can run agents on. Clawboo installs its GitHub release and runs every Hermes agent as a Hermes profile in one Hermes gateway that Clawboo starts and watches. It keeps its own memory, skills and scheduled jobs between runs. See Hermes. Home: the first row of the sidebar’s nav, one page per team with a team picker like the Board’s (and All teams). It shows what needs you, the team’s goals and their progress, its KPIs, work in flight, spend, routines and its pinned pages. Clicking a team’s icon on the team rail opens it on that team. See Home.L
Leader: a badge Clawboo gives the team member whose name or role reads as a lead when you deploy a team template. Boo Zero still leads the team. The Leader leads the team’s chats only when your install has no Boo Zero. See Teams.M
Marketplace: ready-made agents, teams and skills that you deploy with a click. Clawboo downloads the full catalog from GitHub; offline, it shows a built-in set of 5 teams and 15 agents. See Marketplace. MCP: the Model Context Protocol, an open standard for giving AI agents tools from another program. Agents reach Clawboo’s board, memory and tools through Clawboo’s own MCP servers, and most connectors are MCP servers too. See MCP servers. Meet your team: the introduction a team’s chat shows on your first visit: the team’s agents, then a few words from you about who you are. The agent that answers you in any of the team’s chats receives your introduction with your message. See Team chat. Memory: the facts your agents save and share, shown in the sidebar’s Memory view as a graph and a list. An agent on a team reads its team’s facts and the global ones. See Memory. Mission: a task together with every task handed off under it. A budget can cover one mission. See Budgets and guardrails. Model: the AI model an agent runs on, such as a Claude model, a GPT model or a local Ollama model. You pick a default, and you can change the model per agent. See Connect providers and runtimes.N
Needs you: the Board’s first column. It holds approvals and every task that waits on a person: one that failed, timed out, was stopped, is blocked, has no agent, needs review, or never started. See Board.O
Ollama: a free program that runs AI models on your own computer. Clawboo Native can run agents on it with no API key. See Connect providers and runtimes. OpenClaw: an open-source agent runtime that runs its own Gateway on your computer. Clawboo can run agents on it next to its other runtimes. See OpenClaw. OpenClaw Gateway: the program OpenClaw runs on your computer. Clawboo connects to it to create, run and chat with OpenClaw agents. See OpenClaw. Org chart: every agent on every team on one live chart, around Boo Zero. Open it from the sidebar or withCmd/Ctrl + 1. See Org chart and team graphs.
P
Peer chat: the shared channel where teammates on different runtimes post updates to each other while they work. You do not see it in the dashboard; your chats with a team are General and its rooms. See How agents talk to each other. Permissions: the Permissions section on an agent’s page, under Details. On Clawboo Native it holds the switch that lets the agent ask to run shell commands. On OpenClaw it sets when the agent asks before running a command, and lists the commands it may run without asking. See Command permissions. Personality: the presets and sliders on an agent’s page that set its tone. Clawboo writes the result into the agent’s SOUL.md. See Agents. Provider: the service that runs an AI model, such as Anthropic, OpenAI, OpenRouter or your own Ollama. You connect one with an API key or a sign-in. Clawboo is free; the provider bills any usage. See Connect providers and runtimes.R
Room: a smaller chat inside a team, with some of its members. It has its own conversation, task cards and graph, while the team’s rules, brief, memory and board stay team-wide. Boo Zero leads every room. Deleting a room archives it. See Team chat. Route: a line on the Org chart from one agent to another, meaning “this agent hands work to that one”. It is a line in the first agent’s AGENTS.md, and only OpenClaw agents follow it. See Org chart and team graphs. Routine: work that runs on a schedule. A team routine posts its instructions in the team’s chat for Boo Zero; an agent routine gives one agent a task. See Routines. Runtime: the engine that runs an agent: Clawboo Native (built in), OpenClaw, Claude Code, Codex or Hermes. A team can mix runtimes. See Choose a runtime.S
Settings: one window with three groups. Workspace holds Providers, Runtimes, Memory, Capabilities and Routines; Insights holds Fleet, Tokens Used, Observability and Governance; System holds System and System Health. Open it from the sidebar or withCmd/Ctrl + ,. See Tour the dashboard.
Share: to give an agent a connector. Pick it under Who can use it? in the connector’s detail pane, or on the graph pull a thread off its Boo and pick the connector, or drop a connector tile onto the Boo. Dragging a tile from another agent’s ring asks for Read, Write or Admin access. Stop sharing takes it back from one agent. See Connectors.
Sign in with ChatGPT: connects Codex to your ChatGPT plan instead of an API key. Hermes and OpenClaw can use the plan too, each with its own sign-in. Clawboo Native cannot. See Connect providers and runtimes.
Skill: a label for something an agent is good at, picked from the Marketplace’s Skills tab or on the graph. It shows on the agent’s ring and in the Capabilities panel, but gives the agent no new tool and does not change its instructions. Hermes agents also write skill files of their own, which Hermes reads. See Capabilities.
Standing permission: a command an OpenClaw agent may run without asking again, recorded when you answer Always to its command approval. You see and remove them in the agent’s Permissions section. See Command permissions.
Steer: to reply on a task while an agent is working on it, so the agent reads your reply during the run. A reply reaches the task’s agent at any other status too: a waiting task starts again, and a finished one offers Send as a follow-up task. Reply from the Board’s task drawer, a team chat’s Tasks card or the agent’s Tasks & Routines card. See Steer a running task.
System Health: Settings > System > System Health: Clawboo’s startup checks, with a way to run them again. See System Health.
T
Task: one piece of work on the Board, usually with an agent, a status and comments. See Board. Task folder: the folder of one task that a Claude Code, Codex, Hermes or Clawboo Native agent runs without a worktree,teams/<team id>/tasks/<task id> in the work folder. Each run of the task starts there and is asked to save the task’s files there, and the task’s Files section on the Board shows them. See Task folders.
Task runner: one of the two ways Clawboo runs agents. It runs agent routines on Clawboo Native, Claude Code, Codex and Hermes, and runs started through the API. Only the task runner gives a run that names a git repository its own worktree and stops runs that go nowhere. Most work runs in team chat instead. See How a team works.
Tasks card: the card beside a team chat that sorts the chat’s tasks into Needs you, In progress, To do, Done and Cancelled. Open a task there to read its comments, steer it, or open it on the Board. An agent’s page has a Tasks & Routines card instead. See Team chat.
Team: a group of agents that work together, with its own chats, rules, brief and memory. Deploy one from the Marketplace or build your own. See Teams.
Team chat: a team’s conversations: General and any rooms. When you send a message that @mentions no one, Boo Zero answers it or hands the work to a teammate. See Team chat.
Team folder: the folder a team’s agents share, teams/<team id> in the work folder (~/clawboo-work by default). Turns that hold no task and one-to-one chats start there, and each task folder sits inside it, under tasks/. Deleting the team deletes it. See The work folder.
Team graph: the card beside a team’s chat that draws the team, with each agent’s live status. In a room it is the Room graph. See Org chart and team graphs.
Team rules: short rules that every member of a team follows on every turn in that team’s chats. Edit them with the team’s brief, or add one with /rule in a chat. See Teams.
Tokens Used: Settings > Insights > Tokens Used: recorded token use and cost by team and agent, for every runtime. See Budgets and spend.
Trace: the record of one task-runner run, with its steps, tool calls and errors, shown in the Observability panel. See Observability.
V
Vault: Clawboo’s encrypted store for the keys you connect, kept in your Clawboo folder. Keys you save under Providers are also copied, unencrypted, into OpenClaw’s files. See Where keys are stored. Verification: Clawboo’s check on finished work. It runs the project’s test command, and for bigger changes a second agent reviews the work. It runs for task-runner runs that worked in their own git worktree and changed files, and for team chat work that changed the team’s folder on a team with a work check. Other work is never checked. See How work is checked.W
Worktree: a separate working copy of a git repository, on its own branch, where one task’s file changes stay apart from other work. It is not a sandbox: the agent can still reach the rest of your computer. See Worktrees and handoff.Names in the app
The dashboard’s labels are the names these docs use. The right-hand column lists older or other names you may meet in earlier releases, older pages, or elsewhere.For developers
Code names and architecture terms
Code names and architecture terms
Related
- Tour the dashboard: where each of these things lives on screen.
- Key concepts: the ideas behind the terms, in reading order.
- Known issues: what does not work yet, and what to do about it.
- FAQ: short answers to common questions.