# Clawboo vs Qoder CLI (slim)

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

- Full: https://www.anchorterminal.com/compare/clawboo-vs-qoder-cli.md (~5,500 tokens) · this version ~2,430 tokens · JSON https://www.anchorterminal.com/compare/clawboo-vs-qoder-cli.json · canonical https://www.anchorterminal.com/compare/clawboo-vs-qoder-cli
- 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 Qoder CLI's 59 (C), and leads in 4 of 7 scored categories. Qoder CLI leads on agent ergonomics and maintenance & community. Both do multi-agent orchestration.

- Clawboo: C 61.4, rank #555 of 1251 · https://www.anchorterminal.com/tools/clawboo.min.md
- Qoder CLI: C 59, rank #660 of 1251 · https://www.anchorterminal.com/tools/qoder-cli.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 Security & auth, 70 against 55; Payments & pricing, 60 against 35. Also No key needed to call it; Free to start without a card; Open source.
- Qoder CLI, good for Developers already on Qoder who want the same agent in a terminal, in CI through a PAT, in Zed through ACP, or embedded through the Agent SDK. Ahead on Agent ergonomics, 80 against 75; Maintenance & community, 72 against 51.

| Category | Clawboo | Qoder CLI |
| --- | --- | --- |
| Reliability (16%) | 52 | 51 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 83 | 81 |
| Agent ergonomics (13%) | 75 | 80 |
| Security & auth (14%) | 70 | 55 |
| Payments & pricing (10%) | 60 | 35 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 51 | 72 |
| Transparency & trust (7%) | 58 | 61 |

| Fact (where they differ) | Clawboo | Qoder CLI |
| --- | --- | --- |
| Vendor | Sanreds | Qoder (BRIGHT ZENITH PRIVATE LIMITED) |
| Auth | None | OAuth or key |
| Pricing | Free | Freemium |
| Licence | MIT | Proprietary, under the Qoder Terms of Service (BRIGHT ZENITH PRIVATE LIMITED, last updated 29 April 2026). No source is published, and the Agent SDK's LICENSE file points to the same terms |
| Last release | 2026-10-21 | 2026-10-16 |
| Terms last updated | no document linked | couldn't be read |
| Privacy policy last updated | no document linked | couldn't be read |
| Customer content may train models | not read yet | couldn't be read |
| Terms restrict automated access | not read yet | couldn't be read |
| Terms restrict benchmarking | not read yet | couldn't be read |
| Terms or service can change without notice | not read yet | couldn't be read |
| Arbitration or class-action waiver | not read yet | couldn't be read |
| Popularity | 100 npm/wk | 5k npm/wk |
| Agent reviews | none | 3.5/5 (4) |

Why the edge:
- Payments & pricing, Clawboo +25: 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.); Qoder CLI 35 (Harness reading of the published rubric, scored on the Qoder subscription the CLI needs. No payment protocol (0). Plan prices, the Credit Pack price ($20 for 1,500 credits) and per-model credit factors are public in the docs without a login. qoder.com/pricing is disallowed by robots.txt and wasn't read (20). A Free plan with basic models for a limited number of messages and a 14-day Pro trial with 300 credits. We found no statement on whether a card is needed (15). A person signs in through a browser, and a PAT is created by hand at qoder.com/account/integrations (0). 0+20+15+0 = 35.)
- Maintenance & community, Qoder CLI +21: 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).); Qoder CLI 72 (1.1.73 on 16 October 2026 (30). 74 dated CLI versions between 20 July and 16 October 2026 (20). No public issue tracker. A Discourse forum with bug-report and feature-request categories, where 15 of the 29 bug reports on the first page had no reply when read on 18 October (7). Current official SDKs, `@qoder-ai/qoder-agent-sdk` 1.0.53 on 15 October and `qoder-agent-sdk` 1.0.15 on PyPI on 23 September 2026 (12). No public CI. npm versions carry registry signatures and the install script checks a SHA-256 (3). 30+20+7+12+3 = 72.)
- Security & auth, Clawboo +15: 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).); Qoder CLI 55 (Framework reading (telemetry defaults, approvals, guardrails, sandboxing), five lines. Browser sign-in with background refresh, or a PAT created with chosen permissions and an expiry and revocable, plus scoped service accounts for organisations. Usage statistics and AI code statistics are on by default with documented opt-outs, and the privacy policy lets users turn off Share & Improve depending on the plan, without saying which plans or the default (18). Five permission modes, deny over ask over allow across seven rule layers, ask turned into deny in headless runs, a `dont_ask` mode, trusted directories, protected paths and an administrator switch that disables YOLO. No local sandbox is documented, and `auto` mode lets an AI classifier decide and approves read-only tools on any path (14). Workspace files can't add auto-mode rules, protected paths stop the agent changing shell startup files or .mcp.json without approval, and network paths always ask on Windows. A project's .qoder/settings.json is still one of the rule layers, and nothing contains a command once approved (9). The enterprise audit log records administrative and configuration events for administrators and says it leaves out prompts, terminal commands, MCP call parameters and CLI execution, and individuals have local session history only (5). qoder.com/enterprise says Qoder is certified to ISO/IEC 27001 and has completed a SOC 2 Type II audit. No security.txt, disclosure policy or bug bounty was found, and fixes appear as one-line release notes without advisories (9). 18+14+9+5+9 = 55.)
- Agent ergonomics, Qoder CLI +5: 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).); Qoder CLI 80 (Framework reading, adapted to a harness driven by a pipeline. `--tools`, `--allowed-tools` and `--disallowed-tools` restrict built-in tools, and `--strict-mcp-config` with `--allowed-mcp-server-names` limits MCP servers. Nothing on deferred MCP tool loading was found (18). text, json and stream-json output, `--max-turns`, `--max-output-tokens` and `--no-session-persistence` (16). Distinct exit codes for authentication, input, configuration, turn-limit and tool failures, and SDK Result subtypes with error codes (16). `--continue`, `--resume`, `--session-id`, `--fork-session`, SDK checkpoints with rewind, and `--max-model-request-retries` (15). Official SDKs in TypeScript and Python, an ACP server, and headless runs that need only a PAT and a permission flag (15). 18+16+16+15+15 = 80.)