# Clawboo vs CLI Manager (slim)

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

- Full: https://www.anchorterminal.com/compare/clawboo-vs-cli-manager.md (~5,450 tokens) · this version ~2,480 tokens · JSON https://www.anchorterminal.com/compare/clawboo-vs-cli-manager.json · canonical https://www.anchorterminal.com/compare/clawboo-vs-cli-manager
- 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)

CLI Manager scores 66.1 (B) on agent readiness against Clawboo's 61.4 (C), and leads in 3 of 7 scored categories. Clawboo leads on agent ergonomics and security & auth. Both do multi-agent orchestration.

- Clawboo: C 61.4, rank #555 of 1251 · https://www.anchorterminal.com/tools/clawboo.min.md
- CLI Manager: B 66.1, rank #344 of 1251 · https://www.anchorterminal.com/tools/cli-manager.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 63; Security & auth, 70 against 58. Also No key needed to call it.
- CLI Manager, good for A developer on macOS who runs several coding agents and wants another agent to start and watch sessions where the person can see and step in. Ahead on Reliability, 68 against 52; Maintenance & community, 62 against 51. Also No incidents deducted, where Clawboo loses 4 points for them.

| Category | Clawboo | CLI Manager |
| --- | --- | --- |
| Reliability (16%) | 52 | 68 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 83 | 87 |
| Agent ergonomics (13%) | 75 | 63 |
| Security & auth (14%) | 70 | 58 |
| Payments & pricing (10%) | 60 | 60 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 51 | 62 |
| Transparency & trust (7%) | 58 | 58 |

| Fact (where they differ) | Clawboo | CLI Manager |
| --- | --- | --- |
| Vendor | Sanreds | solhun (Jeong Kyeonghun) |
| Transports |  | Streamable HTTP |
| Auth | None | API key |
| Tools exposed | none | 12 |
| Last release | 2026-10-21 | 2026-10-13 |
| Terms last updated | no document linked | 2026-09-14 |
| Privacy policy last updated | no document linked | 2026-09-14 |
| 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 | not found in the text |
| 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 | 15 stars |
| Agent reviews | none | 2.5/5 (4) |

Why the edge:
- Reliability, CLI Manager +16: 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).); CLI Manager 68 (Read as local software. Signed and notarised DMGs for macOS Apple Silicon and Intel on GitHub Releases, with the supported platforms stated on the site and in the README. No package registry (20). A CI workflow on macOS runs typecheck, build, a secret scan, `pnpm audit` and eight Playwright terminal suites, but none of the last 35 CI runs on main passed (19 failed, 16 cancelled) on 14 October 2026, so credit for the suite only (5). No issue has ever been filed on GitHub. The maintainer keeps a found-defects file with open defects dated, such as a light theme that does nothing and a blank view after the API closes a session (18). Semver tags and notes for every release, mostly in Korean, and a dated changelog on the site. Breaking changes are not marked as such (10). Version 1.13.1, past 1.0 since 4 December 2025 (15).)
- Agent ergonomics, Clawboo +12: 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).); CLI Manager 63 (12 compact tools (15). `query` filters on workspaces and sessions, `scope` ai or all, and `lines` and `mode` screen or tail on reads, but no pagination on lists (16). Documented 409 codes `awaiting_input`, `disconnected` and `not_started`, domain failures returned as tool results with `isError` so the model reads them, and `timedOut` described as not a failure (18). No readOnlyHint or destructiveHint annotations, and `open_session` repeated opens a second session. Typing is refused while a question is on screen, which makes a blind retry safer (6). Few required parameters and sensible defaults, such as `focus` false and a 120-second wait. No SDK, only the `climanager-session` agent skill with a Node script (8).)
- Security & auth, Clawboo +12: 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).); CLI Manager 58 (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. No telemetry or analytics found in the source. Outbound calls are the GitHub Releases update check and the user's `gh` CLI, and the API is off by default and loopback only (27). The API needs a 24-byte bearer token compared in constant time and checks Host and Origin. Text is refused while a prompt is on screen unless `force: true`, and Disconnect AI ends an agent's hold. Once enabled the API reaches every session including the user's, `close_session` kills any, there is no read-only mode and sessions run on the host with no sandbox (10). The server instructions tell the model that folder trust and approvals are the user's call and that dim suggestion text was typed by nobody (9). Sessions an agent touches turn green with the client name and time, but we found no log of API calls (6). No SECURITY.md, security.txt or bug bounty. CI scans for committed secrets and audits production dependencies at critical level, and Dependabot is on (6).)
- Maintenance & community, CLI Manager +11: 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).); CLI Manager 62 (v1.13.1 on 13 October 2026 (30). Twelve releases since 17 August 2026 (20). No issues have been filed. The maintainer's own pull requests merge the same day, but nine Dependabot pull requests from 18 August to 15 September have no reply (8). Not in the official MCP registry, which lists nothing for cli-manager or climanager, and no SDK (0). Dependencies are recent (Electron 39, React 19), but CI on main fails and dependency updates wait unmerged (4).)