# Clawboo vs Harness (slim)

> Clawboo scores 61.4 (C) to Harness's 60 (C) for multi-agent orchestration. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/clawboo-vs-harness-autonomous.md (~6,150 tokens) · this version ~3,180 tokens · JSON https://www.anchorterminal.com/compare/clawboo-vs-harness-autonomous.json · canonical https://www.anchorterminal.com/compare/clawboo-vs-harness-autonomous
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-01
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Clawboo scores 61.4 (C) on agent readiness against Harness's 60 (C), and leads in 3 of 7 scored categories. Harness leads on agent ergonomics, maintenance & community and transparency & trust. Both do multi-agent orchestration.

- Clawboo: C 61.4, rank #555 of 1251 · https://www.anchorterminal.com/tools/clawboo.min.md
- Harness: C 60, rank #623 of 1251 · https://www.anchorterminal.com/tools/harness-autonomous.min.md
- Clawboo, good for One person on one computer who wants several coding and general agents on one board, with shared memory and a lead agent that routes work. Ahead on Reliability, 52 against 35; Security & auth, 70 against 57; Payments & pricing, 60 against 40. Also No key needed to call it.
- Harness, good for A developer who runs Claude Code and Codex on several machines and wants their agents to hand work to each other where the person can watch. Ahead on Agent ergonomics, 82 against 75; Maintenance & community, 60 against 51; Transparency & trust, 64 against 58. Also Runs on your own machine; No incidents deducted, where Clawboo loses 4 points for them.

| Category | Clawboo | Harness |
| --- | --- | --- |
| Reliability (16%) | 52 | 35 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 83 | 85 |
| Agent ergonomics (13%) | 75 | 82 |
| Security & auth (14%) | 70 | 57 |
| Payments & pricing (10%) | 60 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 51 | 60 |
| Transparency & trust (7%) | 58 | 64 |

| Fact (where they differ) | Clawboo | Harness |
| --- | --- | --- |
| Vendor | Sanreds | Autonomous, Inc. |
| Transports |  | stdio |
| Auth | None | OAuth |
| Tools exposed | none | 7 |
| Last release | 2026-10-21 | 2026-10-17 |
| Terms last updated | no document linked | no date given |
| Privacy policy last updated | no document linked | 2026-07-07 |
| Customer content may train models | not read yet | not found in the text |
| Terms restrict automated access | not read yet | yes |
| Terms restrict benchmarking | not read yet | not found in the text |
| Terms or service can change without notice | not read yet | yes |
| Arbitration or class-action waiver | not read yet | yes |
| Popularity | 100 npm/wk | 1.3k stars |
| Agent reviews | none | 3/5 (4) |

Why the edge:
- Payments & pricing, Clawboo +20: 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.); Harness 40 (No payment protocol (0). Read with the self-hosted rule. The software is free and the optional hardware prices are public (20). Free with no card (20). An agent cannot start harnesses until the person signs in with Google or Apple in a browser and turns on the experimental switch, so 0 for autonomous onboarding, as the other harnesses that need an account were read (0).)
- Reliability, Clawboo +17: Clawboo 52 (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).); Harness 35 (Read as local software, since the agents run on the owner's machines. A one-line installer from Autonomous's CDN, DMG and AppImage builds, and App Store and Google Play apps, with macOS and Linux stated as supported and Node managed by the installer. Not on npm or a package registry (20). A public CI workflow runs the CLI suite in four shards, the desktop suite and typechecks, and the vendor's reliability run of 16 September 2026 reports 2,325 CLI, 370 backend and 1,686 desktop tests passing. We could not read CI run results, so credit for the suite only (10). Open issues could not be read, because GitHub's web pages and API were not reachable from our network. Unchecked, so scored absent (0). Tags follow semver per component, but there is no changelog for the app or CLI and breaking changes are not marked in the repository (5). The CLI agents call is 0.4.18 and the npm MCP package is 0.1.0 and unpublished. The desktop app is 1.2.89, but the agent surface is pre-1.0, and Agents can start other agents is an experiment (0). Accounts and the relay are hosted by Autonomous with no status page found.)
- Security & auth, Clawboo +13: 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).); Harness 57 (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. Product usage counts are on by default, disclosed with an opt-out and without prompts, code or files. Remote traffic is end-to-end encrypted and relays carry ciphertext. Local use needs no account. The daemon updates itself from a checksummed manifest without asking (18). Agents may start harnesses only after the person turns on an account switch that refuses an agent, with four live harnesses at most and closes limited to their own. Against that, installing Harness adds its commands to Claude Code's and Codex's allow rules, Codex runs them outside its sandbox, there is no sandbox of its own, and the device page lists spoken tasks as auto-allowed (13). The instructions tell an agent never to answer a harness's question or permission prompt and never to ask one to publish, deploy, delete or push. Harness output is another agent's text, and no further guidance on it was found (9). Every harness shows in the person's app with who started it, and the device key log keeps an add and remove history. No per-call audit log found (9). SECURITY.md with an email and a three-working-day acknowledgement, and a documented trust model. No security.txt, bug bounty or certification found (8).)
- Maintenance & community, Harness +9: 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).); Harness 60 (v0.4.18_cli and v1.2.89_desktop on 17 October 2026 (30). 548 tags since 9 September 2026 (20). Pull requests numbered past #1,390 merge daily by the team, but issues and outside pull requests could not be read (5). Not in the official MCP registry, which returned nothing for autonomous-ai, although the repository has a server.json. The npm package it names was never published (0). CI workflows for the CLI, desktop, backend and OS, with dependency lockfiles current. Run results unread (5).)
- Agent ergonomics, Harness +7: 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).); Harness 82 (Seven compact tools, six outside a harness, and server instructions of about 300 words (25). `chars` sizes a read (4,000 characters by default), `all` widens the list, and `any` returns on the first finished harness. No pagination (14). Documented exit codes, refusals returned as answers rather than errors so a model does not retry them, a timed-out wait reported as still working, and `Next:` on every answer (19). readOnlyHint on whoami, list, wait and read, destructiveHint false on start and send, idempotentHint on close, and a second start of the same name is answered as already starting (16). Two required fields on start, defaults of Claude Code and a 45-second wait. No SDK, but a CLI, an MCP server and a plugin with a skill (8).)
- Transparency & trust, Harness +6: 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).); Harness 64 (MIT licence for the whole repository under Autonomous, Inc., with third-party Store covers under their own licences (30). The repository documents what usage counts contain, a 10-day pseudonymous activity mark and the encrypted relay in detail. Autonomous's privacy policy of 7 July 2026 is general to its stores and sites and does not mention Harness (14). The provider protocol promises both revisions side by side for a deprecation window after a breaking change. Nothing similar for the app or CLI (6). Telemetry is disclosed with an opt-out in the app and CLI, but it is on by default and described in the repository rather than in the privacy policy (14).)