# Clawboo vs Unstoppable (slim)

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

- Full: https://www.anchorterminal.com/compare/clawboo-vs-unstoppable.md (~6,250 tokens) · this version ~3,080 tokens · JSON https://www.anchorterminal.com/compare/clawboo-vs-unstoppable.json · canonical https://www.anchorterminal.com/compare/clawboo-vs-unstoppable
- 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 Unstoppable's 34.7 (F), and leads in 6 of 7 scored categories. Unstoppable leads on maintenance & community. Both do multi-agent orchestration.

- Clawboo: C 61.4, rank #555 of 1251 · https://www.anchorterminal.com/tools/clawboo.min.md
- Unstoppable: F 34.7, rank #1164 of 1251 · https://www.anchorterminal.com/tools/unstoppable.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 45; Schema & documentation, 83 against 30; Agent ergonomics, 75 against 5; Security & auth, 70 against 36; Payments & pricing, 60 against 30. Also Open source.
- Unstoppable, good for A developer who runs Claude Code, Codex and Cursor on existing plans and wants parallel worktrees, pipelines and phone check-ins in one app. Ahead on Maintenance & community, 58 against 51. Also No incidents deducted, where Clawboo loses 4 points for them.

| Category | Clawboo | Unstoppable |
| --- | --- | --- |
| Reliability (16%) | 52 | 45 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 83 | 30 |
| Agent ergonomics (13%) | 75 | 5 |
| Security & auth (14%) | 70 | 36 |
| Payments & pricing (10%) | 60 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 51 | 58 |
| Transparency & trust (7%) | 58 | 56 |

| Fact (where they differ) | Clawboo | Unstoppable |
| --- | --- | --- |
| Vendor | Sanreds | Unstoppable Domains, Inc. |
| Pricing | Free | Freemium |
| Licence | MIT | Proprietary, under Unstoppable Domains, Inc.'s Terms of Service. No source published |
| Last release | 2026-10-21 | 2026-10-23 |
| Terms last updated | no document linked | 2026-10-06 |
| Privacy policy last updated | no document linked | 2026-10-08 |
| Customer content may train models | not read yet | not found in the text |
| Terms restrict automated access | not read yet | not found in the text |
| Terms restrict benchmarking | not read yet | yes |
| Terms or service can change without notice | not read yet | not found in the text |
| Arbitration or class-action waiver | not read yet | yes |
| Popularity | 100 npm/wk | none |

Why the edge:
- Agent ergonomics, Clawboo +70: 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).); Unstoppable 5 (These lines measure an interface an agent calls, and Unstoppable has none, so context cost, output controls and retries score nothing. For the person, a usage limit shows choices to wait for the reset or continue on credits (2 of 20). Guest use with no account, a first-run page that imports Claude and Codex projects, and few required settings. No SDK (3 of 15). Total 5.)
- Schema & documentation, Clawboo +53: Clawboo 83 (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).); Unstoppable 30 (Graded on the interface an outside agent can use, which is none. No API, OpenAPI file, MCP server or documented command (0). unstoppable.ai/llms.txt lists the product, help and policy pages in Markdown (10). Twenty-two dated help articles explain for a person what each part does and when to use it, such as Code and Work modes and approval modes (5 of 20). No typed inputs an agent could call (0). Step-by-step examples for people and named error states such as usage limit reached and update failed, with no error responses for an agent (3 of 15). Numbered versions and a public dated changelog, which lists only four releases from 20 to 23 October 2026 (12 of 15). Total 30.)
- Security & auth, Clawboo +34: 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).); Unstoppable 36 (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. Activity sharing is Off for every activity type by default and secrets are removed before upload, but the privacy policy also collects usage telemetry (feature use, session activity, token and spend metrics, diagnostics) with no opt-out stated, and updates download automatically by default (15 of 30). Ask and Accept edits modes with allow and deny rules by command, file write, MCP tool and network host, deny winning, and safety rules that block force-pushes and destructive deletes. Every kind of chat starts in Full access, which skips prompts and safety rules, and local agents have no documented sandbox. Cloud worktrees get their own sandbox (8 of 20). The in-app browser stops agents acting on private sign-in pages. No other guidance on untrusted content from web pages, MCP servers or connected tools (3 of 15). Cost and usage panels, a team feed with tool-use metadata, approval rules with their origin, and an Audit Trail experiment in Labs (8 of 15). Two-factor authentication for accounts. No security.txt on unstoppable.ai, the parent's security.txt expired on 22 January 2024, its bug bounty policy link returns 404, and no SOC 2 or ISO 27001 found (2 of 20). Total 36.)
- Payments & pricing, Clawboo +30: 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.); Unstoppable 30 (No x402, MPP or L402 (0). The app is published as free, but AI credit prices appear only after sign-in, and no pricing page exists (unstoppable.ai/pricing redirects to the home page). Plan prices of $19, $29 and $49 appear only in an 11 August 2026 blog post (10). Guest use with no account, and 10 free AI credits a day with no card (20). A person has to download and install the app, so no autonomous onboarding (0). Total 30.)
- Reliability, Clawboo +7: 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).); Unstoppable 45 (Read as local software, because the product is the desktop app the owner runs, as for the other harnesses. Signed downloads for macOS Apple Silicon, macOS Intel and Windows on the download page, version 1.15.0, plus iOS and Android apps in the stores, with the supported platforms stated. No package registry (20). Closed source with no public CI or test suite (0). No public issue tracker. Bugs go through in-app feedback, email and Discord, none of which shows a record we could read (0). Version numbers and a dated changelog, but only 1.12.0 to 1.15.0 are listed and breaking changes are not marked as such (10). Version 1.15.0 (15). The hosted parts (accounts, AI credits, cloud agents, Remote Control) have no status page. status.unstoppabledomains.com covers the domains business only.)
- Maintenance & community, Unstoppable +7: 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).); Unstoppable 58 (Read for a closed product. Version 1.15.0 on 23 October 2026, and iOS 1.1.9 on 27 October (30). Four desktop releases from 20 to 23 October and nine iOS updates since 11 August 2026 (20). A public changelog, a support email, in-app feedback and a Discord server, none tested for replies. Help articles were updated between 19 and 24 October (6 of 15). No SDK and no MCP registry entry (0). Windows updates check signatures per the 1.13.0 notes, with no build pipeline to inspect (2 of 10). Total 58.)