# Clawboo

> Clawboo is an open-source, self-hosted dashboard and server that runs a team of AI agents on one task board. A lead agent, Boo Zero, hands tasks to Claude Code, Codex, Hermes, OpenClaw or Clawboo's own built-in agents.

- Canonical: https://www.anchorterminal.com/tools/clawboo
- Pricing: https://www.anchorterminal.com/tools/clawboo#pricing
- Reviews: https://www.anchorterminal.com/tools/clawboo#reviews
- Markdown: https://www.anchorterminal.com/tools/clawboo.md (~8,150 tokens)
- Slim: https://www.anchorterminal.com/tools/clawboo.min.md (~1,630 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/tools/clawboo.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT clawboo.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-01

## Overview

**Grade C · 61.4/100 · rank #555 of 1251 · #15 in Agent harnesses · not agent-ready · confidence medium**


## Assessment

Tasks, memory, team chat and connectors are shared across five runtimes through four MCP servers, with documentation that states each default and limit. Claude Code, Codex and Hermes run with their sandboxes and approval prompts off and no setting to change it, and a reverse-proxy exposure of the MCP servers is fixed only on the unreleased main branch.

## Facts

| Field | Value |
| --- | --- |
| Vendor | Sanreds (https://www.claw.boo) |
| Kind | Agent harness |
| Category | Agent harnesses (https://www.anchorterminal.com/categories/agent-harnesses) |
| Auth | None · No Clawboo account. On the default loopback bind the API needs no credential. An optional shared token, `STUDIO_ACCESS_TOKEN`, puts every `/api/` route behind a `clawboo_access` cookie, with no users, roles or per-person revocation. Agents Clawboo starts reach its MCP servers through signed attach URLs. |
| Pricing | Free (Free · OSS) · Free and MIT, self-hosted, with nothing to buy. The owner pays the model providers or plans each runtime uses, or runs a local Ollama model with no key. No hosted option is offered. |
| x402 | No · No x402, MPP or L402 in the documentation (llms-full.txt), the README or the npm package metadata (checked 2026-11-01). |
| Licence | MIT |
| Packages | npm: `clawboo` |
| Source | https://github.com/clawboo/clawboo |
| Docs | https://docs.claw.boo |
| llms.txt | https://docs.claw.boo/llms.txt |
| Last release | 2026-10-21 |
| npm downloads / week | 100 |
| Interfaces | Web dashboard and REST API (199 routes per the API overview) on `http://localhost:18790`, the `clawboo` CLI, and four MCP servers (Tasks, Memory, Tools, TeamChat) over Streamable HTTP at `/api/mcp/*` or as the stdio bins `clawboo-mcp-*` |
| Runtimes | Clawboo Native (its own agents on 11 providers, including a local Ollama), Claude Code through the Claude Agent SDK, Codex through `codex app-server`, Hermes, and an OpenClaw Gateway |
| Approvals | Clawboo Native shell commands are off by default and asked one at a time when on. Connector calls that change something ask first, and a run that has read private data and untrusted content asks before any outbound connector call. Hand-offs naming words such as delete, deploy or production wait for a person |
| Sandbox | None. Claude Code, Codex and Hermes run with their own prompts and sandboxes off, as the owner's user. A git worktree separates file changes and is not a fence |
| Network | Loopback bind by default, with a same-origin guard on every `/api/` request. No egress controls for agents. Only connector calls pass through Clawboo |
| MCP client | Curated connectors, entries from the official MCP registry, custom stdio or HTTP servers with OAuth dynamic client registration, and apps through Composio, each shared per agent at Read, Write or Admin |
| Models | The owner's provider keys, a ChatGPT plan through Codex, or a local Ollama model with no key |
| Headless | `POST /api/teams/:id/chat` and `POST /api/runtimes/:id/run` on the REST API, routines on a cron schedule, and the MCP stdio bins |
| Telemetry | None per the docs. The server fetches the marketplace catalogue from GitHub, the latest version from npm and OpenRouter's public model list, and the dashboard loads its font from Google Fonts and the GitHub star count |
| Releases in 90 days | 2 (0.4.0 on 28 September and 0.5.0 on 21 October 2026), with a security fix and other changes listed as unreleased on main |
| Storage | SQLite at `~/.clawboo/clawboo.db` and an AES-256-GCM vault whose key sits beside it. Keys saved under Providers are also written in plain text to `~/.openclaw/.env` |
| Hosted option | None. The README roadmap lists hosted and organisation deployments as not yet shipped |
| Capabilities | agent.multi-agent, agent.mcp-client |
| Tags | open-source, self-hosted, local, free, no-card, llms-txt, mcp, typescript |
| JSON | https://www.anchorterminal.com/api/v1/tools/clawboo.json |

## Score breakdown (methodology v0.7, October 2026 research run)

Assessed 2026-11-01 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points.

| Category | Weight | This run | Score (0–100) | Points |
| --- | --- | --- | --- | --- |
| Reliability | 16% | 20 | 52 | 10.4 |
| Performance | 10% | pending | pending | n/a |
| Schema & documentation | 13% | 16.2 | 83 | 13.5 |
| Agent ergonomics | 13% | 16.2 | 75 | 12.2 |
| Security & auth | 14% | 17.5 | 70 | 12.2 |
| Payments & pricing | 10% | 12.5 | 60 | 7.5 |
| Task success | 10% | pending | pending | n/a |
| Maintenance & community | 7% | 8.8 | 51 | 4.5 |
| Transparency & trust (editorial 80, provenance 36) | 7% | 8.8 | 58 | 5.1 |
| Negative events | up to −15 | up to −15 | Undated advisory on the security page, read 1 November 2026. On 0.5.0 (21 October 2026) and older, any request from 127.0.0.1 reaches `/api/mcp/` without the access cookie, so a reverse proxy on the same machine exposes the boards, memory, team chat, tools and signed attach URLs for any agent, even with `STUDIO_ACCESS_TOKEN` set. Published by the maintainer with a proxy rule to block it, fixed on main and not released, in a setup that isn't the default, -3. https://docs.claw.boo/operating/security Listed under Unreleased in the changelog, read 1 November 2026. On 0.5.0 and older, an access token containing a character outside letters, digits and `.`, `_`, `~`, `-` turned the access check off while the server kept running, leaving a proxied dashboard open. Fixed on main and not released, -1. https://docs.claw.boo/appendices/changelog  | -4 |
| **Total** | | | | **61.4 → C** |

### Why each score

- Reliability 52 (checked 2026-11-01): Read as local software. The official npm package `clawboo` states Node.js 22.12 or newer, and the README says macOS, Linux and Windows are supported (20). `ci.yml` runs lint, typecheck, Vitest and a real-concurrency suite on Linux and platform suites on Windows and macOS, and `publish.yml` reruns build, lint, typecheck, tests and a clean-install boot before it publishes. 0.5.0 carries provenance from that workflow on main, so its checks passed at that commit, but run results on main couldn't be read (15). github.com was unreachable, so open crash and regression issues are unchecked. A known-issues page lists 25 entries with a status each, three of them fixed on main (5). Changesets write a changelog entry per release, and removals and the 0.2.0 database reset are called out, though breaking changes arrive in minor versions before 1.0 (12). Version 0.5.0, and SECURITY.md says pre-1.0 (0).
- Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes.
- Schema & documentation 83 (checked 2026-11-01): Harness reading of the framework line, as for Paperclip. The REST API's 199 routes are documented per resource with parameters, bodies and responses, and the MCP tools reference gives typed arguments for every tool on the four servers, but no OpenAPI file was found (17). llms.txt, llms-full.txt and a Markdown copy of every page at `.md` on docs.claw.boo (10). The docs say what each part does and does not cover, with known issues, production defaults and a limits page that names the code line behind each number (17). Tool arguments are typed with required and optional fields and documented caps, such as 24 live subtasks per parent and limits lowered to 1,000, with free-text task bodies (12). curl examples on each API page, an events and errors reference, and the exact error strings each MCP tool returns (14). A dated changelog for every release with an Unreleased section, though API paths carry no version and every MCP server reports 0.1.0 (13).
- Agent ergonomics 75 (checked 2026-11-01): Harness reading, scored on what an agent or pipeline driving it has to supply. Four MCP servers keep tool lists small (12 Tasks tools, 4 Memory tools, 2 or 3 TeamChat tools, and Tools with four demonstration builtins plus granted connectors), Clawboo Native gets a read-only Tasks subset, and Tools results over 16 KiB are trimmed with a handle to read the rest (22). Circuit breakers stop task-runner runs after more than 30 tool calls or 200,000 tokens a minute, and team chat caps hand-offs at 8 a turn and three levels. Budgets warn only unless set to a hard cap, and a hard cap stops most runs only between runs (14). REST errors use one `{error}` shape, refused MCP calls return `denied:` with a reason prefix, and 429s carry `Retry-After` (16). `claim_task` and `assign_task` are atomic, illegal status changes are refused by name, the board survives restarts and routines resume after failure. No MCP tool annotations are documented (14). One `npx` command and a provider key or a local Ollama, but Claude Code teammates need a global install with the Agent SDK, and there is no client SDK (9).
- Security & auth 70 (checked 2026-11-01): Harness reading of the framework checklist, as for the other harnesses. 30 for what leaves the machine by default, 20 for approvals and sandboxing, 15 for prompt-injection posture, 15 for audit and 20 for the security programme. The docs say Clawboo sends no telemetry and list the GitHub catalogue fetch, the npm version check, OpenRouter's public model list, Google Fonts and the GitHub star count, of which only the catalogue address can be changed (27). Clawboo Native shell commands are off by default and asked one at a time, and connector grants are per agent with approval on writes. Claude Code, Codex and Hermes run with their prompts and sandboxes off and no setting to change it, they can read Clawboo's database and key vault, and with no access token by default any local program can answer approval cards (8). Images in agent text don't load on their own, peer posts are marked as evidence, and a run that has read private data and untrusted content asks before any outbound connector call (11). An audit log of budget, breaker, approval, verification, tool-call and install events, with secrets masked (13). SECURITY.md with private reporting, CodeQL, Dependabot and npm provenance. No security.txt or bug bounty, OSV lists no advisory for `clawboo`, and the proxy advisory is on the docs with a workaround while its fix is unreleased (11).
- Payments & pricing 60 (checked 2026-11-01): No payment protocol (0). Read with the self-hosted rule. Free under MIT with nothing to buy (20). No card and no Clawboo account (20). One `npx` command installs and starts it with no sign-up (20). Model costs belong to the providers the owner connects.
- Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored.
- Maintenance & community 51 (checked 2026-11-01): 0.5.0 was published to npm on 21 October 2026 (30). Two releases in the 90 days to 1 November 2026, 0.4.0 on 28 September and 0.5.0, below the three the line asks for (0). github.com was unreachable, so replies to issues, pull requests and Discussions are unchecked. The CI file cites issue #140 as fixed (3). One public npm package, current, with no entry in the official MCP registry for its four servers (10). CI, CodeQL, weekly Dependabot and SLSA provenance on 0.4.0 and 0.5.0, with `@composio/client` pinned to an alpha (8).
- Transparency & trust 58 (checked 2026-11-01): MIT, Copyright 2026 Sanreds, with a third-party notices file (30). The docs list every file Clawboo writes, which copies of keys are encrypted and which are plain text, retention for stored tool results (7 days) and pending approvals (24 hours), and that prompts go only to connected providers. There is no privacy statement, and the website wasn't read (22). The 0.1.x line is deprecated on npm with a note in the changelog, and removals are dated in release notes, with no written deprecation policy or notice period (10). No telemetry, with the server's own outbound requests disclosed, though the npm update check has no setting (18).

Fix list, everything this grade says the listing lacks, the biggest gain first (20 items). What it covers is at https://www.anchorterminal.com/fixes/clawboo.md (JSON https://www.anchorterminal.com/fixes/clawboo.json). The whole list for a coding agent comes from `POST https://www.anchorterminal.com/api/v1/fix-list` with `{"listing": "clawboo", "plan": "read"}`, free while the beta runs

### What we couldn't check

- unchecked: github.com and api.github.com were unreachable, so stars, open issues, reply times, Actions results on main, tags and GitHub security advisories weren't read
- unchecked: www.claw.boo, whose robots.txt disallows Claude-Web, so any terms, privacy page or claims on the website weren't read
- The proxy advisory has no date and no GitHub advisory or CVE was found. Whether a release after 0.5.0 ships, and when, is open
- The X summary called Clawboo a 31 October 2026 launch. npm shows a name placeholder on 28 February 2026, the first real release on 19 May 2026 and 0.5.0 on 21 October 2026
- Judgement call. Clawboo Native runs its own model loop with file and shell tools, but Clawboo mostly drives other harnesses like Paperclip does, so `agent.harness` is left out of its capabilities as it is for Paperclip (founder, 1 November 2026)
- No person's name is published. Sanreds is the copyright holder and npm maintainer, and no company, terms or address was found

### Sources

- repository README (product, quickstart, runtimes, roadmap): <https://raw.githubusercontent.com/clawboo/clawboo/main/README.md> (seen 2026-11-01)
- MIT licence (copyright holder): <https://raw.githubusercontent.com/clawboo/clawboo/main/LICENSE> (seen 2026-11-01)
- SECURITY.md (reporting, CodeQL, Dependabot, provenance, threat model): <https://raw.githubusercontent.com/clawboo/clawboo/main/SECURITY.md> (seen 2026-11-01)
- CLI changelog: <https://raw.githubusercontent.com/clawboo/clawboo/main/apps/cli/CHANGELOG.md> (seen 2026-11-01)
- CI workflow: <https://raw.githubusercontent.com/clawboo/clawboo/main/.github/workflows/ci.yml> (seen 2026-11-01)
- Dependabot configuration: <https://raw.githubusercontent.com/clawboo/clawboo/main/.github/dependabot.yml> (seen 2026-11-01)
- npm registry document (versions, dates, maintainer, bins, engines): <https://registry.npmjs.org/clawboo> (seen 2026-11-01)
- npm provenance attestation for 0.5.0: <https://registry.npmjs.org/-/npm/v1/attestations/clawboo@0.5.0> (seen 2026-11-01)
- npm weekly downloads: <https://api.npmjs.org/downloads/point/last-week/clawboo> (seen 2026-11-01)
- docs llms.txt: <https://docs.claw.boo/llms.txt> (seen 2026-11-01)
- docs llms-full.txt (every docs page): <https://docs.claw.boo/llms-full.txt> (seen 2026-11-01)
- changelog with Unreleased section: <https://docs.claw.boo/appendices/changelog> (seen 2026-11-01)
- security model and proxy advisory: <https://docs.claw.boo/operating/security> (seen 2026-11-01)
- what agents can do (runtime permissions): <https://docs.claw.boo/concepts/permissions> (seen 2026-11-01)
- production defaults (what leaves the machine): <https://docs.claw.boo/operating/production-defaults> (seen 2026-11-01)
- MCP servers and attach tokens: <https://docs.claw.boo/operating/mcp-servers> (seen 2026-11-01)
- MCP tools reference: <https://docs.claw.boo/reference/mcp-tools> (seen 2026-11-01)
- REST API overview (auth, rate limits, errors, routes): <https://docs.claw.boo/reference/rest-api> (seen 2026-11-01)
- known issues and limitations: <https://docs.claw.boo/appendices/known-issues> (seen 2026-11-01)
- release process: <https://docs.claw.boo/internals/release-process> (seen 2026-11-01)
- licence and third-party notices: <https://docs.claw.boo/appendices/license-and-notices> (seen 2026-11-01)
- security.txt on docs.claw.boo (404): <https://docs.claw.boo/.well-known/security.txt> (seen 2026-11-01)
- official MCP registry search for clawboo (no entries): <https://registry.modelcontextprotocol.io/v0/servers?search=clawboo> (seen 2026-11-01)
- OSV query for npm clawboo (no advisories): <https://api.osv.dev/v1/query> (seen 2026-11-01)
- robots.txt of www.claw.boo: <https://www.claw.boo/robots.txt> (seen 2026-11-01)

## Score history

Every move of a score since the listing was graded, newest first, with its cause. A score can't move without an entry here. JSON: https://www.anchorterminal.com/api/v1/tools/clawboo/history.json

- 2026-11-01: graded 61.4 C (methodology 0.7)

## Who's behind it (provenance 36/100, checked 2026-11-01)

| Check | Finding | Points |
| --- | --- | --- |
| Legal entity named | not found | 0/20 |
| Domain age | claw.boo, no registry record we could read | 0/15 |
| Endpoint on the vendor's domain | no hosted endpoint | n/a |
| Terms of service | nothing hosted, so the MIT licence stands in | 10/10 |
| Privacy policy | nothing hosted, not scored | n/a |
| Status page | not found | 0/10 |
| Changelog | published | 10/10 |
| security.txt | not found | 0/10 |
| People named | 1 named with their role, none with a public profile | 7/10 |
| Support route | help pages, a community | 5/5 |

No legal entity is named in the repository, the docs or the npm package. The MIT licence reads Copyright (c) 2026 Sanreds, and the npm package's only maintainer is sanreds.

www.claw.boo was not read. Its robots.txt disallows Claude-Web in Cloudflare's managed block and later allows ClaudeBot and anthropic-ai, so the site's terms and privacy pages, if any, are unchecked.

docs.claw.boo/.well-known/security.txt answered 404 on 1 November 2026. SECURITY.md sends reports to GitHub private vulnerability reporting.

The software is self-hosted, so there is no vendor endpoint or status page to check. The domain registration date was not looked up.

### Terms and privacy, as read

A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice.

**Terms of service**. Nothing is hosted by the vendor, so there are no terms of service to read. The MIT licence stands in and the check scores in full.


**Privacy policy**. Nothing is hosted by the vendor, so there is no privacy policy to read and the check isn't scored.


## Humans behind the project (researched 2026-11-01 from public pages, not part of the grade)

### Key people

- Sanreds, Copyright holder of Clawboo's MIT licence and maintainer of the clawboo npm package (a handle)
- Note: Clawboo publishes no personal name. The MIT licence and the docs' licence page name the copyright holder as Sanreds (2026), and the npm package's only maintainer and publisher is the account sanreds. Whether Sanreds is one person or a group isn't stated, so founder isn't set and no personal accounts are listed; the npm contact address is left out as a personal address. The GitHub organisation clawboo's profile says "We build open-source tooling for orchestrating teams of AI agents." No company, registration or address was found in the repository, the docs or the npm package. www.claw.boo wasn't read (its robots.txt disallows Claude-Web), and github.com couldn't be reached, so the maintainer's GitHub profile wasn't read. Investors were looked for in the README, the docs, the npm package and two web searches; none was found and no funding is mentioned. The README's roadmap lists hosted and organisation deployments as not yet shipped.
- Clawboo (Sanreds): GitHub https://github.com/clawboo

### Getting support

- Help: https://docs.claw.boo/help/troubleshooting
- Help: https://docs.claw.boo/appendices/known-issues
- Help: https://github.com/clawboo/clawboo/issues
- Community (GitHub Discussions): https://github.com/clawboo/clawboo/discussions
- Sources: https://raw.githubusercontent.com/clawboo/clawboo/main/LICENSE, https://raw.githubusercontent.com/clawboo/clawboo/main/README.md, https://raw.githubusercontent.com/clawboo/clawboo/main/SECURITY.md, https://raw.githubusercontent.com/clawboo/.github/main/profile/README.md, https://registry.npmjs.org/clawboo, https://docs.claw.boo/appendices/license-and-notices

## Probe metrics

Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score.

## Strengths

- One board, one team chat and one shared memory across Clawboo Native, Claude Code, Codex, Hermes and OpenClaw agents
- No telemetry per the docs, which list the three requests the server makes itself and the two the dashboard makes
- Loopback bind by default, a same-origin guard against browser and DNS-rebinding attacks, and a refusal to start on a network bind without a token
- About 120 documentation pages, served as Markdown with llms.txt and llms-full.txt, including a known-issues page and every built-in limit with its source line
- npm releases carry SLSA provenance from the repository's publish workflow, with CodeQL and Dependabot in the repository

## Weaknesses

- Claude Code runs in `bypassPermissions`, Codex with `danger-full-access` and Hermes with `--yolo`, with no setting to change it and no sandbox
- On 0.5.0 and older, a same-machine reverse proxy exposes `/api/mcp/` without the access cookie. The fix is on main and unreleased on 1 November 2026
- No access token by default, so any local program can call the API and answer approval cards
- Keys saved under Providers are also written in plain text to `~/.openclaw/.env` and each OpenClaw agent's `auth-profiles.json`
- Version 0.5.0, with two releases in the 90 days to 1 November 2026 and budgets that only warn unless set to a hard cap



## Before you call it (notes for agents)

1. Run `npx clawboo@latest`, not a bare `npx clawboo`, which can reuse an older cached build. Node.js 22.12 or newer is required
2. On 0.5.0 behind nginx, Caddy or a Cloudflare Tunnel, deny `/api/mcp/` at the proxy and set `STUDIO_ACCESS_TOKEN` from `openssl rand -hex 24`
3. Give Claude Code, Codex and Hermes teammates only work you would let run unattended, or run Clawboo under a separate user account or VM
4. Create a hard-cap budget in Settings > Insights > Governance before long runs. A fresh install has no budget and new budgets only warn
5. Install `@anthropic-ai/claude-agent-sdk` globally beside Clawboo for Claude Code teammates. A one-off `npx` run cannot load it

## Connect

Install:

```bash
npx clawboo@latest   # Node.js 22.12 or newer
```

First request:

```bash
curl http://localhost:18790/api/health
```

Headless / CI:

```json
{
  "command": "curl -X POST http://localhost:18790/api/teams/\u003cteam-id\u003e/chat -H 'Content-Type: application/json' -d '{\"message\":\"Plan the launch checklist.\"}'"
}
```

## Similar tools

Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last.

| Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown |
| --- | --- | --- | --- | --- | --- | --- |
| OpenAI Agents SDK | AA | 86.2 | 1 | agent.multi-agent, agent.mcp-client | no | https://www.anchorterminal.com/tools/openai-agents-sdk.md |
| Pydantic AI | A | 81.9 | 5 | agent.multi-agent, agent.mcp-client | no | https://www.anchorterminal.com/tools/pydantic-ai.md |
| Microsoft Agent Framework | A | 79.4 | 10 | agent.multi-agent, agent.mcp-client | no | https://www.anchorterminal.com/tools/microsoft-agent-framework.md |
| Docker Agent | BB | 76.6 | 38 | agent.multi-agent, agent.mcp-client | no | https://www.anchorterminal.com/tools/docker-agent.md |
| goose | BB | 74.3 | 78 | agent.mcp-client, agent.multi-agent | no | https://www.anchorterminal.com/tools/goose.md |
| Agent Development Kit (ADK) | BB | 73.7 | 87 | agent.multi-agent, agent.mcp-client | no | https://www.anchorterminal.com/tools/google-adk.md |

## Panel reviews (0)

Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): .

Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md

## Notable

- Claude Code runs in `bypassPermissions`, Codex with approval `never` and sandbox `danger-full-access`, and Hermes with `--yolo`, and the docs say no setting changes this (source: <https://docs.claw.boo/concepts/permissions>)
- The security page carries an advisory that on 0.5.0 and older a reverse proxy on the same machine reaches `/api/mcp/`, including `/api/mcp/config`, without the access cookie. Fixed on main, not released on 1 November 2026 (source: <https://docs.claw.boo/operating/security>)
- No telemetry per the docs, which list the requests the server and dashboard make on their own (source: <https://docs.claw.boo/operating/production-defaults>)
- 0.4.0 and 0.5.0 on npm carry SLSA provenance from `.github/workflows/publish.yml` in clawboo/clawboo (source: <https://registry.npmjs.org/-/npm/v1/attestations/clawboo@0.5.0>)
- 0.1.0 of 28 February 2026 was a placeholder for the npm name. 0.1.1 of 19 May 2026 is the first real release, and every 0.1.x release is deprecated on npm (source: <https://docs.claw.boo/appendices/changelog>)

- #15 of 45 in Best agent harnesses and coding agents: https://www.anchorterminal.com/best/agent-harnesses/index.md
- All 955 harnesses comparisons: https://www.anchorterminal.com/compare/agent-harnesses/index.md

## Compare

- [Amp vs Clawboo](https://www.anchorterminal.com/compare/amp-vs-clawboo.md): C 57.1 vs C 61.4
- [Antigravity CLI vs Clawboo](https://www.anchorterminal.com/compare/antigravity-cli-vs-clawboo.md): C 57.6 vs C 61.4
- [Auggie CLI vs Clawboo](https://www.anchorterminal.com/compare/auggie-vs-clawboo.md): D 51 vs C 61.4
- [Claude Code vs Clawboo](https://www.anchorterminal.com/compare/claude-code-vs-clawboo.md): C 59.9 vs C 61.4
- [Clawboo vs CLI Manager](https://www.anchorterminal.com/compare/clawboo-vs-cli-manager.md): C 61.4 vs B 66.1
- [Clawboo vs Cline](https://www.anchorterminal.com/compare/clawboo-vs-cline.md): C 61.4 vs C 60.5
- [Clawboo vs Crush](https://www.anchorterminal.com/compare/clawboo-vs-crush.md): C 61.4 vs C 56.7
- [Clawboo vs DeepSeek Harness (dsh)](https://www.anchorterminal.com/compare/clawboo-vs-deepseek-harness.md): C 61.4 vs D 49.5
- [Clawboo vs dsh-superagent (DeepSeek)](https://www.anchorterminal.com/compare/clawboo-vs-deepseek-superagent.md): C 61.4 vs E 42.1
- [Clawboo vs Devin](https://www.anchorterminal.com/compare/clawboo-vs-devin.md): C 61.4 vs C 55.8
- [Clawboo vs Droid CLI](https://www.anchorterminal.com/compare/clawboo-vs-droid-cli.md): C 61.4 vs C 59.2
- [Clawboo vs Gemini CLI](https://www.anchorterminal.com/compare/clawboo-vs-gemini-cli.md): C 61.4 vs B 66.8
- [Clawboo vs GitHub Copilot CLI](https://www.anchorterminal.com/compare/clawboo-vs-github-copilot-cli.md): C 61.4 vs C 58.4
- [Clawboo vs goose](https://www.anchorterminal.com/compare/clawboo-vs-goose.md): C 61.4 vs BB 74.3
- [Clawboo vs Harness](https://www.anchorterminal.com/compare/clawboo-vs-harness-autonomous.md): C 61.4 vs C 60
- [Clawboo vs HarnessRouter](https://www.anchorterminal.com/compare/clawboo-vs-harnessrouter.md): C 61.4 vs D 53.3
- [Clawboo vs Jules](https://www.anchorterminal.com/compare/clawboo-vs-jules.md): C 61.4 vs E 44.7
- [Clawboo vs Junie CLI](https://www.anchorterminal.com/compare/clawboo-vs-junie.md): C 61.4 vs D 53.1
- [Clawboo vs Kilo Code CLI](https://www.anchorterminal.com/compare/clawboo-vs-kilo-code-cli.md): C 61.4 vs BB 73
- [Clawboo vs Kimi Code CLI](https://www.anchorterminal.com/compare/clawboo-vs-kimi-code-cli.md): C 61.4 vs B 62.1
- [Clawboo vs Kiro CLI](https://www.anchorterminal.com/compare/clawboo-vs-kiro-cli.md): C 61.4 vs C 60.8
- [Clawboo vs MiniMax Code](https://www.anchorterminal.com/compare/clawboo-vs-minimax-code.md): C 61.4 vs B 67.7
- [Clawboo vs Mistral Vibe CLI](https://www.anchorterminal.com/compare/clawboo-vs-mistral-vibe-cli.md): C 61.4 vs B 63
- [Clawboo vs Muse Code](https://www.anchorterminal.com/compare/clawboo-vs-muse-code.md): C 61.4 vs C 61.2
- [Clawboo vs OpenCode](https://www.anchorterminal.com/compare/clawboo-vs-opencode.md): C 61.4 vs B 68.8
- [Clawboo vs OpenHands](https://www.anchorterminal.com/compare/clawboo-vs-openhands.md): C 61.4 vs BB 71
- [Clawboo vs OpenMausBot](https://www.anchorterminal.com/compare/clawboo-vs-openmausbot.md): C 61.4 vs B 65.4
- [Clawboo vs Paperclip](https://www.anchorterminal.com/compare/clawboo-vs-paperclip.md): C 61.4 vs C 59
- [Clawboo vs Parallax](https://www.anchorterminal.com/compare/clawboo-vs-parallax-agents.md): C 61.4 vs E 38.1
- [Clawboo vs Prime Agent](https://www.anchorterminal.com/compare/clawboo-vs-prime-agent.md): C 61.4 vs C 60.7
- [Clawboo vs Qoder CLI](https://www.anchorterminal.com/compare/clawboo-vs-qoder-cli.md): C 61.4 vs C 59
- [Clawboo vs Qwen Code](https://www.anchorterminal.com/compare/clawboo-vs-qwen-code.md): C 61.4 vs BB 72.6
- [Clawboo vs Mirror CLI](https://www.anchorterminal.com/compare/clawboo-vs-reflection-mirror.md): C 61.4 vs C 54.1
- [Clawboo vs Rovo Dev CLI](https://www.anchorterminal.com/compare/clawboo-vs-rovo-dev-cli.md): C 61.4 vs E 44.1
- [Clawboo vs Unstoppable](https://www.anchorterminal.com/compare/clawboo-vs-unstoppable.md): C 61.4 vs F 34.7
- [Clawboo vs Vibe-Trading](https://www.anchorterminal.com/compare/clawboo-vs-vibe-trading.md): C 61.4 vs B 62.8
- [Clawboo vs Warp (Warp Agent CLI and the Oz Agent API)](https://www.anchorterminal.com/compare/clawboo-vs-warp.md): C 61.4 vs C 59.6

## Verify this listing

For the vendor. The badge or a plain link to this page verifies the listing, from a page on claw.boo or one of its subdomains, or the README at the root of github.com/clawboo/clawboo. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "clawboo", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify

HTML badge:

```html
<a href="https://www.anchorterminal.com/tools/clawboo"><img src="https://www.anchorterminal.com/badges/clawboo.svg" alt="Clawboo on Anchor Terminal" height="20"></a>
```

Markdown badge, for a README:

```markdown
[![Clawboo on Anchor Terminal](https://www.anchorterminal.com/badges/clawboo.svg)](https://www.anchorterminal.com/tools/clawboo)
```

Plain link:

```html
<a href="https://www.anchorterminal.com/tools/clawboo">Clawboo on Anchor Terminal</a>
```

## Share this listing

For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Clawboo is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score.

- Dark: https://www.anchorterminal.com/assets/share/clawboo-dark.png
- Light: https://www.anchorterminal.com/assets/share/clawboo-light.png
- Create a video and download its frames: https://www.anchorterminal.com/assets/listing-video/index.html?listing=clawboo

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
