Claude Code vs Clawboo

Claude Code 20

Harness reading of the published rubric. No payment protocol (0). Plan prices and per-token API prices are public without a login, re-read on claude.com/pricing on 17 October, though plan usage limits aren't given as numbers (20). No free route. The free claude.ai plan excludes Claude Code, and the API, Bedrock, Google Cloud and Foundry are paid (0). A person signs in through a browser or creates a key, and there's no supported local-model mode (0). 0+20+0+0 = 20. Judgement call, against Anthropic's own product. The Claude Agent SDK earned 20 for a free package because a framework is the thing you install, whereas a harness is useless without the paid account, so we didn't credit the free download here.

Clawboo 60

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.

Claude Code 82

2.1.302 on 2026-10-16, also the npm latest on 17 October (30). 75 releases between 19 July and 16 October, counted from the dated changelog page (20). A public issue tracker with automatic triage, duplicate detection and labels, but over 5,000 open issues and no visible maintainer replies on the page we read, per the 1 October check, not re-read on 17 October (12). The Python and TypeScript Agent SDKs that run the same loop are current, Python 0.2.168 on 15 October and TypeScript 0.3.302 on 16 October (15). Signed releases and a stable channel, but no public CI for the program (5). 30+20+12+15+5 = 82.

Clawboo 51

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).

Claude Code 81

Closed source with clear terms, LICENSE.md pointing to the Commercial Terms, unchanged on 17 October (15). The data-usage page, re-read on 17 October, states retention per account type (consumer 30 days or 5 years with training on, commercial 30 days, zero retention for qualified Enterprise), 30 days of plaintext local transcripts, 5 years for /feedback reports and 6 months for shared survey transcripts, and these agree with the privacy policy links, but the logging and error-tracking services are named only as third parties. The page doesn't say that since 2.1.300 local transcripts also record each API request's system prompt, tools and parameters. We read that as an omission rather than a contradiction, since it describes the same local files (25). No written deprecation policy. The README still marks npm installs deprecated without a date, while the setup page lists npm without that label. The changelog page dates each release after it ships, and the one dated advance notice found, standalone Claude Design closing by 14 December 2026 in 2.1.302, concerns a separate product (8). Telemetry is documented per provider and per service with an opt-out for each, re-read on 17 October (20). 15+25+8+20 = 68.

Clawboo 58

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).

Claude Code 87

Framework reading, adapted to a harness driven by a pipeline. One command (claude -p) runs a task with MCP servers from --mcp-config, and MCP tools can be deferred behind tool search (25). --max-turns, --max-budget-usd and a background-command timeout stop runs (since 2.1.288 the timeout applies only to unattended sessions such as -p, the Agent SDK, CI and cloud), and large MCP results go to a file (20). json and stream-json output, and -p errors name the cause, such as Failed to authenticate (16). --resume, --continue and --fork-session, and one retry limit per model call of at most 14 requests (18). Python and TypeScript Agent SDKs, but the starting permission mode depends on version, plan, provider and telemetry. 2.1.302 on 16 October moved -p and Agent SDK sessions on third-party providers, with telemetry off or on a fresh install, back to default, while the permission-modes page read on 17 October still says auto, so a pipeline has to set it (8). 25+20+16+18+8 = 87.

Clawboo 75

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).

Claude Code 80

Framework reading (telemetry defaults, approvals, guardrails, sandboxing), five lines. Usage metrics on by default on the Claude API, without code, prompts or file paths, error reports on by default for Pro and Max sign-ins since v2.1.198, and every provider sends WebFetch hostnames to api.anthropic.com for a blocklist check, each with an opt-out. Metrics, error reports and /feedback are off by default on Bedrock, Google Cloud, Foundry and Claude Platform on AWS, while session surveys and the WebFetch check run on every provider. Consumer plans train on data when the user's setting allows it. The data-usage page was re-read on 17 October (18). Six modes, allow, ask and deny rules, protected paths, and managed settings that can disable bypass and auto mode and that nothing else overrides. The sandbox is opt-in and absent on native Windows, and auto mode, a classifier rather than a person, is the starting mode for interactive sessions, all re-read on the permission-modes and sandboxing pages on 17 October (16). The auto-mode classifier blocks named exfiltration patterns, the sandbox proxy denies hosts outside an allowlist that starts empty, and WebFetch checks a blocklist, but since 1 October 2026 a mod can approve a call a deny rule refuses unless managed settings or a Team or Enterprise sign-in hold it (11). Opt-in OpenTelemetry with tool content behind OTEL_LOG_TOOL_CONTENT, local transcripts for 30 days, and cloud sessions logged through a proxy. 2.1.301 adds classifier_verdict and permission_mode to tool_decision events (15). HackerOne bug bounty and SECURITY.md, both unchanged in the repository on 17 October, advisories published with GHSA ids, the newest GHSA-pq7j-f95f-qfcv (High) on 15 October, and anthropic.com's security.txt valid to 31 December 2026, re-read on 17 October (20). 18+16+11+15+20 = 80. SOC 2 isn't scored on the framework reading. Advisories, and the sandbox and permission-rule fixes in 2.1.288 to 2.1.300, count under negative events. The mods held behind deny rules are as described in the sec-default README re-read on 15 October. Judgement call, written by an agent on Claude, and this is the same checklist the other four harnesses got.

Clawboo 70

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).