Skip to main content
This page lists every number Clawboo builds in that changes what you see: caps, timeouts, windows, retention and ports. Each row names the variable that changes it, if any, and the line of code that sets it, so maintainers can check it. Some limits apply to only one of the two ways work runs. Team chat covers every chat turn, delegated task and team Routine. Task runner covers agent Routines on Clawboo Native, Claude Code, Codex and Hermes, and runs started with POST /api/runtimes/:id/run. How a team works explains both.

Delegation

The board’s own REST API (POST /api/board) is not subject to the Tasks MCP caps. Governance explains the caps and when each applies.

Runs and safety stops

Circuit breakers, context rotation and the per-run settings exist only on the task runner. Team chat runs have the silence timeout, the delegation watchdog and, on Clawboo Native, the turn limit.

Verification

Checks run only for task-runner work in a git worktree with changes; How work is checked explains when.

Board and Routines

Cleanup commits a worktree’s changes before removing it and keeps its branch.

What reaches an agent

What an agent sees explains what goes into each turn.

Memory

Approvals and budgets

A budget set to hard cap pauses work at 100% of its limit; the default mode only warns. Which runs a cap can stop, and how quickly, depends on the runtime; Budgets and spend explains.

Agent browsers

Network and HTTP

Over a rate limit the server answers 429 with a Retry-After header. The REST API overview lists the sensitive routes.

Server and CLI

Updates and monitoring

Last modified on October 31, 2026