# Clawboo vs Warp (Warp Agent CLI and the Oz Agent API) (slim)

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

- Full: https://www.anchorterminal.com/compare/clawboo-vs-warp.md (~7,300 tokens) · this version ~3,730 tokens · JSON https://www.anchorterminal.com/compare/clawboo-vs-warp.json · canonical https://www.anchorterminal.com/compare/clawboo-vs-warp
- 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 Warp (Warp Agent CLI and the Oz Agent API)'s 59.6 (C), and leads in 3 of 7 scored categories. Warp (Warp Agent CLI and the Oz Agent API) leads on schema & documentation, 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
- Warp (Warp Agent CLI and the Oz Agent API): C 59.6, rank #639 of 1251 · https://www.anchorterminal.com/tools/warp.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 Agent ergonomics, 75 against 66; Security & auth, 70 against 52; Payments & pricing, 60 against 20. Also No key needed to call it; Free to start without a card.
- Warp (Warp Agent CLI and the Oz Agent API), good for Teams that want one agent across an interactive terminal session and API-started cloud runs, including Claude Code and Codex runs on Warp's infrastructure or their own workers. Ahead on Schema & documentation, 89 against 83; Maintenance & community, 84 against 51; Transparency & trust, 69 against 58.

| Category | Clawboo | Warp (Warp Agent CLI and the Oz Agent API) |
| --- | --- | --- |
| Reliability (16%) | 52 | 52 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 83 | 89 |
| Agent ergonomics (13%) | 75 | 66 |
| Security & auth (14%) | 70 | 52 |
| Payments & pricing (10%) | 60 | 20 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 51 | 84 |
| Transparency & trust (7%) | 58 | 69 |

| Fact (where they differ) | Clawboo | Warp (Warp Agent CLI and the Oz Agent API) |
| --- | --- | --- |
| Vendor | Sanreds | Warp |
| Auth | None | OAuth or key |
| Pricing | Free | Freemium |
| Licence | MIT | Mixed. The client, including the `warp` and `oz` binaries, is AGPL-3.0 with the `warpui_core` and `warpui` crates under MIT. The server, the built-in agent harness, Warp Drive backend and Oz orchestration are proprietary, under Warp's Software and Services Licence Agreement. The SDKs are Apache-2.0 |
| Last release | 2026-10-21 | 2026-10-15 |
| Terms last updated | no document linked | 2025-10-07 |
| Privacy policy last updated | no document linked | 2026-08-18 |
| 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 | yes |
| Terms or service can change without notice | not read yet | not found in the text |
| Arbitration or class-action waiver | not read yet | not found in the text |
| Popularity | 100 npm/wk | none |
| Agent reviews | none | 3.3/5 (4) |

Why the edge:
- Payments & pricing, Clawboo +40: 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.); Warp (Warp Agent CLI and the Oz Agent API) 20 (Harness reading of the published rubric, scored on the Warp plan the agent needs. No payment protocol (0). Plan prices are public, and Warp-provided inference is billed at public API rates on paid plans, but the agent-hour platform rate and compute rate for cloud runs were not on the pricing page (10). Free is $0 and includes Warp Agent CLI access, but no bundled Warp inference, so the agent runs only with purchased usage or your own provider key. Whether sign-up asks for a card was not tested (10). A person signs in through a browser or device code, and API keys are created by hand in the Oz web app or the Warp app (0). 0 + 10 + 10 + 0 = 20.)
- Maintenance & community, Warp (Warp Agent CLI and the Oz Agent API) +33: 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).); Warp (Warp Agent CLI and the Oz Agent API) 84 (Release 2026.10.15 (v0.2026.10.14.08.27), also the version the installer served on 18 October 2026 (30). 15 dated releases between 23 July and 15 October 2026 (20). Issues and pull requests are public on GitHub, with 3.9k open and 7.1k closed issues, 1.5k open and 3.8k closed pull requests, and 925 commits in the 90 days to 18 October 2026, per our GitHub record. The FAQ describes an agent first review then a staff review, with @oss-maintainers for escalation and a Slack community, and the changelog credits outside contributors each week. Maintainer reply times are still unread (12). Official Python and TypeScript SDKs, released 6 October 2026 as 1.0.0 and 2.0.0 (15). CI on every pull request and a checksummed Homebrew cask, but the install script verifies nothing (7). 30 + 20 + 12 + 15 + 7 = 84.)
- Security & auth, Clawboo +18: 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).); Warp (Warp Agent CLI and the Oz Agent API) 52 (Framework reading (telemetry defaults, approvals, guardrails, sandboxing), five lines. The FAQ says the built-in harness runs server-side, so prompts, file contents and command output pass through Warp. The privacy page says AI interactions and console inputs may be collected unless Help improve Warp is off, and the security overview says data collection is on by default for Free and paid teams and off on Business and Enterprise. The opt-out is documented in the desktop app's settings, not for the CLI. Personal and agent keys can expire after 1, 30 or 90 days, and provider keys stay in the device's secure storage (14). Per-action permissions with `always_ask`, `agent_decides` and `always_allow`, edits always shown as a diff under `agent_decides`, a default denylist and child agents asking first. Auto-approve bypasses the user's denylist by default, and no local OS sandbox is documented. Cloud runs use a Docker sandbox as a non-root user with passwordless sudo (11). No prompt-injection guidance was found in the CLI, platform or factory pages read, and secret redaction is off by default (4). Cloud runs record transcripts, tool calls and logs, the API returns timelines and conversations, the app has a Network Log, and the Enterprise Analytics API can filter tool calls for audit (11). SECURITY.md names security@warp.dev and private GitHub advisories, SOC 2 Type II is stated with a trust centre and a subprocessor list. No security.txt and no bug bounty were found, and the GitHub advisory list was not read (12). 14 + 11 + 4 + 11 + 12 = 52.)
- Transparency & trust, Warp (Warp Agent CLI and the Oz Agent API) +11: 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).); Warp (Warp Agent CLI and the Oz Agent API) 69 (The client, including the `warp` and `oz` binaries, is AGPL-3.0, an OSI licence, with the UI crates under MIT. The built-in agent harness, the server and Oz orchestration are proprietary, so the part that runs the agent loop is closed. Judgement call (20). The privacy page says Business and Enterprise are covered by zero data retention, the security overview says ZDR applies across all plans and elsewhere mentions it for Enterprise teams, and the legal security page says it is available on the Enterprise plan. The privacy notice gives criteria rather than retention periods. A subprocessor list and a DPA are linked (15). The Oz CLI carries a legacy notice with a promise of guidance before any support change, and the changelog dates renames such as warp-tui to warp, but there is no written deprecation policy or notice period (8). An exhaustive telemetry event table, Rudderstack and Sentry named, and an opt-out in the app's privacy settings. The CLI pages don't describe what the CLI sends or how to switch it off (14). 20 + 15 + 8 + 14 = 57.)
- Agent ergonomics, Clawboo +9: 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).); Warp (Warp Agent CLI and the Oz Agent API) 66 (Harness reading, adapted to a harness driven by a pipeline. MCP servers are attached per run with `--mcp` or the `mcp_servers` config, and profiles gate MCP calls, but no per-tool disabling or deferred tool loading was found (12). The API lists runs with `limit`, `cursor`, `sort_by`, `state`, `task_status` and `name`, and returns a normalised conversation and a timeline per run. The `warp` CLI has no print mode or JSON output and the Oz CLI's run output is described only as printed tool calls (12). RFC 7807 errors with codes such as `insufficient_credits` and `budget_exceeded`, a `retryable` flag, and since 7 October 2026 unattended CLI runs end as blocked instead of hanging when the agent asks for input. No CLI exit codes are documented (16). Follow-ups, interrupts and cancels by run or conversation ID, `conversation_id` to continue a run, and `warp --resume`. No idempotency key on run creation (14). Python and TypeScript SDKs with retries and timeouts, but a cloud run needs an environment ID and a Warp account with usage, and the `warp` CLI itself can't be driven headless (12). 12 + 12 + 16 + 14 + 12 = 66.)
- Schema & documentation, Warp (Warp Agent CLI and the Oz Agent API) +6: 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).); Warp (Warp Agent CLI and the Oz Agent API) 89 (API reading for the Warp Platform API, with the CLI docs read as a framework. docs.warp.dev/openapi.json is OpenAPI 3.0.0 with 293 component schemas and bearer authentication (25). llms.txt with per-section Markdown bundles, including one for the Warp Agent CLI and one for the Automation Platform (10). The run request schema says when each field applies (prompt unless a skill is given, `on_behalf_of` only for agent keys on team runs), and the CLI permissions page states each default and when auto-approve bypasses the denylist (15). Run modes, states and permission values are enumerated, and request bodies are typed objects (13). Curl and SDK examples throughout, and an error catalogue of RFC 7807 bodies with a machine-readable code, `retryable` flag and trace ID per error (14). The API sits under /api/v1 with info version 1.0.0, and the weekly changelog has an Oz updates section, but there is no API-only changelog (12). 25 + 10 + 15 + 13 + 14 + 12 = 89.)