Skip to main content
Claude Code is Anthropic’s coding agent. Clawboo runs it through the Claude Agent SDK, so a Claude Code agent works with Claude Code’s own tools: it reads and edits files, runs shell commands and fetches web pages. Clawboo records the cost Claude Code reports for each run. Use this page to set it up, see what Clawboo controls on it, and understand what it can do on your computer. To compare it with the other runtimes, see Choose a runtime.

Before you begin

  • Clawboo running, installed any way: npm install -g clawboo, a one-off npx clawboo@latest run, or a source checkout.
  • Node.js 22.12 or newer, with npm.
  • An Anthropic API key from console.anthropic.com. A claude CLI signed in with a Claude subscription is not enough: Clawboo shows Claude Code as connected, and offers it for your agents, only when an Anthropic API key is available.

Set up Claude Code

1

Install the Claude Agent SDK

Open Settings (at the bottom of the left sidebar, or press Cmd+, on macOS and Ctrl+, on Windows or Linux), then Runtimes. On the Claude Code row, click Install, then Install in the panel that opens. Clawboo installs the Claude Agent SDK (@anthropic-ai/claude-agent-sdk@0.3) into its own runtimes folder and shows npm’s output. This works however you run Clawboo, npx included, and needs no sudo and no restart.Clawboo does not ship the SDK, because its Claude Code binary adds about 210 MB to every install. A source checkout already has it in its node_modules, and an SDK you installed next to a global Clawboo keeps working, so there the row reads Needs key or Connected without this step.
2

Check the Claude Code row

You should see the Claude Code row read Needs key, or Connected if an Anthropic key is already saved. A Claude Code run loads the SDK and starts the SDK’s own claude binary, which came with the SDK in the step above, so there is nothing more to install. A claude CLI on your PATH is not used and does not count: without the SDK the row reads Not installed.If the install ends with “The Agent SDK installed without its own <platform>-<arch> binary, so Claude Code could not run on it and nothing was changed”, npm left out the SDK’s platform package, which is an optional dependency. Clawboo keeps no such install, so whatever ran Claude Code before still does. Check that npm may install optional dependencies, then click Install again.
3

Connect your Anthropic key

Click Connect on the row, paste your key into the ANTHROPIC_API_KEY field, and click Connect. Clawboo checks the key with Anthropic before it saves it. If the check fails, the panel shows the reason; fix the key, or click Connect anyway when Anthropic is only unreachable from this computer.You should see the row read Connected. If you already saved an Anthropic key under Settings > Providers, Claude Code reads Connected without this step.
4

Put a Claude Code agent on a team

Create a team, and in Customize team set a member’s runtime to Claude Code, then deploy the team. You can pick Claude Code there only while its row reads Connected; until then it is greyed out with “Connect in Runtimes”. See Teams for the full flow.

What Clawboo controls on Claude Code

Your own Claude Code setup stays out

Clawboo starts Claude Code without your own Claude Code setup. A Claude Code agent does not load:
  • your user settings in ~/.claude/settings.json: plugins, hooks, env, permissions, model and effort level
  • the MCP servers you added to your own Claude Code
  • your ~/.claude/CLAUDE.md and ~/.claude/rules, or a CLAUDE.md in any folder above the one it works in (on a task with no worktree, the team’s folder is the exception; see below)
  • Claude Code’s auto memory, so it neither reads nor writes the notes Claude Code keeps for a repository
It still loads the Claude Code files of the folder it works in. In a task’s worktree that is the repository’s CLAUDE.md, .claude/settings.json (hooks included) and .mcp.json, as anyone who clones the repository gets them. On a task with no worktree it works in the task’s own folder, and it also reads the CLAUDE.md, .claude/CLAUDE.md and .claude/rules/ of the team’s folder and of the tasks/ folder between them, so a CLAUDE.md in the team’s folder reaches its task runs as well as the turns that start there. The team folder’s .claude/settings.json and .mcp.json do not apply on a task run: only the task folder’s own project settings do. This does not change how Claude Code signs in. Clawboo passes your Anthropic key in Claude Code’s environment, and the claude command’s own sign-in is not kept in a settings file. If your Claude Code reaches Anthropic through ~/.claude/settings.json, for example an env block that sets ANTHROPIC_BASE_URL or an apiKeyHelper, that no longer applies to agents: set the same variables in the environment you start Clawboo with. Leaving your setup out is not a sandbox. Claude Code can still read any file your user account can, ~/.claude included.

Permissions and safety

Clawboo starts Claude Code with its permission prompts turned off (permissionMode: 'bypassPermissions'). Nothing asks you before it runs a command, edits or deletes a file, or reaches the network. It runs as your user account and can read and change any file that account can.
  • A worktree is not a sandbox. Only a task-runner run of a task that changes files, with a repository named, works in its own git worktree, which keeps its edits off your main checkout. Everywhere else there is no worktree. A run on a task (one handed out in team chat, one you give from the Board, or a research or review run, which includes every agent Routine you create in the app) starts in the task’s own folder, teams/<team id>/tasks/<task id> in the work folder (~/clawboo-work by default). Turns that hold no task, such as the lead’s turns and your messages in team chat, and the agent’s own chat start in its team’s folder, teams/<team id>, which every member of the team shares (a task or an agent with no team uses teams/_no-team). The work folder sits outside Clawboo’s data folder, so ../.. from there does not reach the database. Work an install keeps in the data folder (see The work folder for when that happens) does not get that distance. That folder only sets where it starts: Claude Code can still read and change any file your user account can, including Clawboo’s database and key vault in ~/.clawboo, by their full path.
  • Clawboo’s approvals do not cover Claude Code’s own tools. Calls the agent makes through Clawboo’s Tools server (connectors, for example) go through Clawboo’s checks and can ask you first. Claude Code’s built-in shell, file and web tools never do.
  • Clawboo hides some secrets from it, by name only. Before a run, Clawboo removes its own secrets (the OpenClaw Gateway token, the dashboard access token and the vault master key) from the environment Claude Code inherits. It also removes a fixed list of common credentials, such as GitHub, npm, cloud, Stripe, Slack and database variables, and the variables that tie a process to a Claude Code session (CLAUDECODE, CLAUDE_CODE_ENTRYPOINT, CLAUDE_CODE_SESSION_ID, CLAUDE_CODE_SESSION_ATTENDED, CLAUDE_CODE_MESSAGING_SOCKET and CLAUDE_CODE_MESSAGING_TOKEN), so a Clawboo started from a terminal inside Claude Code does not hand that session to its agents. Claude Code settings such as CLAUDE_CODE_USE_BEDROCK pass through, like every other variable not on these lists, and credential files on disk stay readable.
  • With a user per agent, each agent has its own ~/.claude. With CLAWBOO_AGENT_USERS (Linux only for now), each Claude Code agent runs as an OS user of its own and uses that user’s ~/.claude, not yours or another agent’s. Give it an API key, or a token from claude setup-token as CLAUDE_CODE_OAUTH_TOKEN.
For work you do not trust, run Clawboo under a separate user account or in a virtual machine. What agents can do compares every runtime.

Costs

Claude Code reports the dollar cost of each run, and Clawboo records that figure as reported, not as an estimate. It counts toward your budgets, and Anthropic bills the same usage to your API key. If a run in team chat or in the agent’s own chat ends without reporting a cost (it failed early, say), Clawboo records an estimate from the length of the prompt and reply instead. The cost arrives when a run finishes, so a hard cap cannot stop a Claude Code run partway through. When that last report takes a hard cap past its limit, the finished result is kept and posted, and the next run is refused. A routine or API run that ends without reporting a cost is estimated the same way as in team chat. See Budgets and spend for how each runtime’s cost reaches your budgets.

Disconnect Claude Code

In Settings > Runtimes, click Manage on the Claude Code row, then Disconnect. This deletes the Anthropic key from Clawboo’s vault. The vault keeps one copy of each key for every runtime, so Clawboo Native and Hermes lose that key too unless they find it elsewhere. Until you connect Claude Code again, it also ignores an Anthropic key in your shell or in ~/.openclaw/.env. To remove one key on purpose, or keep it for other runtimes, see Disconnect a key or a runtime.

Limits

  • Team setup has no model picker for Claude Code members.
  • It needs an Anthropic API key to read Connected; a Claude subscription sign-in alone doesn’t count.
  • The clawboo package does not include the Agent SDK. Install on the Claude Code row adds it.
  • A hard cap counts Claude Code’s cost only when each run ends, so it refuses the next run rather than stopping the current one.

Troubleshooting

The full message continues “which this clawboo install does not ship” and says to install Claude Code from Settings, Runtimes. Clawboo found no Agent SDK, in its runtimes folder or next to Clawboo, and the Claude Code row under Runtimes reads Not installed. Agents already on Claude Code still try to run and fail this way until it is installed.Click Install on the Claude Code row in Settings > Runtimes, then send the message or start the task again.
Clawboo needs an Anthropic API key for Claude Code; the CLI’s own sign-in does not count. Connect a key on the row, or save one under Settings > Providers. An ANTHROPIC_API_KEY set in the environment Clawboo runs with also counts.
The runtime is not connected. Finish Set up Claude Code until the row reads Connected, then open Customize team again.
Anthropic rejected the key. Copy it again from console.anthropic.com, or create a new one, and connect it.
The run reached Anthropic, and Anthropic refused it: a key that is wrong or revoked, an expired sign-in, an account out of credit, or too many requests. The run ends as failed with Anthropic’s own message and the HTTP status, and a task it was working on fails rather than counting as done. Fix the key or the account, then send the message or start the task again.
The key check could not reach Anthropic from this computer. Check your network or proxy. If you are sure the key is right, click Connect anyway to save it without the check.
npm failed while installing the SDK into Clawboo’s runtimes folder (the exit number can differ). The message goes on with npm’s own reason, and the error code is npm’s, such as EACCES or ETARGET. Install never writes to npm’s global folder, so it needs no sudo. Clawboo removed the failed install, and an SDK you already had keeps working. Fix what npm reports, then click Install again.If the message says Clawboo’s runtimes folder must be apart from another folder, or belongs to another user, see When Clawboo will not use it.
The Clawboo server cannot find npm. Install Node.js 22.12 or newer, restart Clawboo with clawboo restart, then click Install again.

Check that it works

  1. In Settings > Runtimes, the Claude Code row reads Connected.
  2. Open the team chat of a team with a Claude Code member. Type @, pick that agent, and ask: “Say hello in one sentence.”
  3. You should see a reply under the agent’s name. If the run fails, the chat shows “The run failed:” and the reason; look it up in Troubleshooting.
  • Clawboo calls the SDK’s query() with permissionMode: 'bypassPermissions' and allowDangerouslySkipPermissions: true. It also passes the run’s working folder (the task’s worktree, the task’s own folder on a task run without one, or else the team’s folder), the model when a run names one, a session to resume, Clawboo’s four MCP servers over HTTP, and the scrubbed environment plus the connected key. It sets settingSources: ['project'], passes settings with autoMemoryEnabled: false and a claudeMdExcludes list that covers every folder above the working folder and your home folder, and sets CLAUDE_CODE_DISABLE_AUTO_MEMORY=1 in the environment, over any value Clawboo itself runs with.
  • Claude Code files its saved sessions under the folder they ran in. When Clawboo moves a team folder into the work folder, it drops the session ids it saved for Claude Code agents (1:1 chat, team chat and task pointers), and when it moves a task checkout, the session id in that checkout’s handoff. The next turn starts a fresh session with the brief and the chat history. Task runs used to start in the team’s folder and now start in the task’s own folder, so once, at the first start with task folders, Clawboo also drops the Claude Code task sessions it saved before, and those tasks start a fresh session on their next run (see Task folders). Codex, Hermes and Clawboo Native agents keep their sessions.
  • The SDK starts Claude Code from its own platform package. The Runtimes row checks for the SDK and that binary, never for a claude CLI. A run loads the SDK from Clawboo’s runtimes folder first, by its file path, else from next to Clawboo (a source checkout’s node_modules, or an SDK installed next to a global Clawboo). A source build of Clawboo uses SDK version 0.3.268.
  • Run a board task on Claude Code directly with POST /api/runtimes/claude-code/run; see the Runtimes API. Such a run falls back to the claude CLI’s own sign-in when no Anthropic key is available.
  • A run that hits Claude Code’s turn limit ends cleanly, and the task runner continues the task in a fresh session with a handoff note. So does a run whose conversation outgrew the model’s context window: it ends out of room rather than failed, with a non-fatal error coded context_overflow that says why. Three values of a result’s terminal_reason mean that: prompt_too_long (the API refused the prompt and compaction could not make it fit), blocking_limit (Claude Code’s own count reached its limit with no compaction to fall back on, so it refused before calling the API) and rapid_refill_breaker (the context refilled to the limit within 3 turns of a compaction, 3 times in a row, so it gave up compacting). Clawboo does not resume such a session. In team chat, where nothing restarts by itself, the task is blocked and its saved session dropped, and Retry runs it in a fresh session. In a one-to-one chat, the next message starts fresh and the chat says so. Claude Code’s own text for these endings, such as advice to use its /clear, is never shown as the agent’s reply. It goes on the board as the failure’s detail, so a task that ran out of room this way says why.
  • An API error reaches the SDK as an assistant message with an error field (authentication_failed, billing_error, rate_limit, …) and then a result with subtype: 'success' and is_error: true. Clawboo reads that pair as a failed run carrying the error value as its code, and does not show the error notice as the agent’s reply. A refused key or login (authentication_failed, oauth_org_not_allowed, cloud_credential_error) is filed as Auth and a refused account (billing_error, account_on_hold, verification_required) as Billing, so the task waits in Needs you with Fix sign-in instead of being retried; see Error classes. Other failed results, such as error_during_execution, keep the cause from their errors list.
Last modified on November 15, 2026