# Clawboo vs Mistral Vibe CLI (slim)

> Mistral Vibe CLI scores 63 (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-mistral-vibe-cli.md (~7,100 tokens) · this version ~3,780 tokens · JSON https://www.anchorterminal.com/compare/clawboo-vs-mistral-vibe-cli.json · canonical https://www.anchorterminal.com/compare/clawboo-vs-mistral-vibe-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)

Mistral Vibe CLI scores 63 (B) on agent readiness against Clawboo's 61.4 (C), and leads in 4 of 7 scored categories. Clawboo leads on schema & documentation and security & auth. Both do multi-agent orchestration.

- Clawboo: C 61.4, rank #555 of 1251 · https://www.anchorterminal.com/tools/clawboo.min.md
- Mistral Vibe CLI: B 63, rank #483 of 1251 · https://www.anchorterminal.com/tools/mistral-vibe-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 Schema & documentation, 83 against 76; Security & auth, 70 against 58. Also No key needed to call it.
- Mistral Vibe CLI, good for Developers and CI jobs that want an open-source harness tuned for Mistral models, with hard per-run budgets and an export file, or a local model with no account. Ahead on Reliability, 69 against 52; Agent ergonomics, 84 against 75; Maintenance & community, 75 against 51; Transparency & trust, 80 against 58.

| Category | Clawboo | Mistral Vibe CLI |
| --- | --- | --- |
| Reliability (16%) | 52 | 69 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 83 | 76 |
| Agent ergonomics (13%) | 75 | 84 |
| Security & auth (14%) | 70 | 58 |
| Payments & pricing (10%) | 60 | 60 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 51 | 75 |
| Transparency & trust (7%) | 58 | 80 |

| Fact (where they differ) | Clawboo | Mistral Vibe CLI |
| --- | --- | --- |
| Vendor | Sanreds | Mistral AI |
| Auth | None | OAuth or key |
| Pricing | Free | Freemium |
| Licence | MIT | Apache-2.0 |
| Read-only variant documented | no | yes |
| Last release | 2026-10-21 | 2026-10-09 |
| Terms last updated | no document linked | 2026-09-25 |
| Privacy policy last updated | no document linked | 2026-09-03 |
| Customer content may train models | not read yet | yes, with an opt-out |
| 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 | yes |
| Arbitration or class-action waiver | not read yet | not found in the text |
| Popularity | 100 npm/wk | 5.1k stars, 332k PyPI/wk |
| Agent reviews | none | 3.3/5 (4) |

Why the edge:
- Maintenance & community, Mistral Vibe CLI +24: 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).); Mistral Vibe CLI 75 (2.26.1 on 9 October 2026 (30). 20 releases on PyPI in the 90 days to 18 October, and 22 in the changelog (20). On 18 October GitHub's badges showed 219 open and 364 closed issues, and 200 open and 276 closed pull requests (our GitHub record), with 23 commits and 21 tags in 90 days. Response times couldn't be read. CONTRIBUTING.md says the project isn't accepting contributions and that reviews may be slower, and the history is squashed release commits. Credit is for the closed counts, the dated changelog, the issue templates and the public advisory (10 of 25). No SDK. `vibe-acp` is current in the ACP registry at 2.26.1 and the Homebrew formula is at 2.26.1 (8 of 15). Dependencies are pinned to exact versions, workflow actions are pinned by commit, and CI runs on main, but no Dependabot or Renovate config was found (7 of 10). 30+20+10+8+7 = 75.)
- Transparency & trust, Mistral Vibe CLI +22: 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).); Mistral Vibe CLI 80 (Apache-2.0, with LICENSE and pyproject in agreement (30). The README sends readers to Mistral's privacy policy (effective 3 September 2026), which names Vibe. The commercial terms (effective 25 September 2026) say no training on customer data unless a product's default or an opt-in allows it, and the pricing page lists model training as opt-out on Free, Pro and Team. The configuration reference calls telemetry anonymous without listing its fields. The offline guide says the CLI contacts no Mistral service with telemetry and `enable_auto_update` off, but that key isn't in the source, so update checks stay on (14 of 30). Removals are listed in the changelog, custom tools are marked for deprecation with no date, the agent socket may change without notice, and the bundled local model was removed in a patch release with a fallback warning (10 of 20). Telemetry is disclosed with an opt-out in the README and the configuration reference, and the README names the server-managed shell-tool rollout, but its fields are only in the source (14 of 20). 30+14+10+14 = 68.)
- Reliability, Mistral Vibe CLI +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).); Mistral Vibe CLI 69 (Local-package reading. PyPI, uv, pip, Homebrew at 2.26.1 and an install script, with Python 3.12 or later stated and UNIX the supported target (20). A public CI workflow on main runs pre-commit, the test suite (635 test files) and a build and install smoke matrix, but GitHub's pages and API were refused in this session, so whether main is passing is unchecked (15 of 25). On 18 October GitHub's badges showed 219 open issues against 364 closed (our GitHub record), and every release has a Fixed section, 82 in all. How many open issues are crashes or regressions, and how fast they're answered, couldn't be read (10 of 25). The changelog states Keep a Changelog and semver and marks breaking changes, but the hooks rename shipped in minor 2.21.0, patch 2.11.1 changed the `-p` approval default, and patch 2.26.1 removed the bundled local model (9). 2.26.1, classified Production/Stable (15). 20+15+10+9+15 = 69.)
- 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).); Mistral Vibe CLI 58 (Framework reading (telemetry defaults, approvals, guardrails, sandboxing), five lines. Telemetry and crash reporting are on by default with an opt-out, and the source sends tool names, approval decisions, the model and file counts to api.mistral.ai only when a Mistral key is set. Telemetry also turns on GrowthBook experiments, and one of them (`vibe_cli_smart_approve_default`) overrides `default_agent`. Credentials are Mistral keys in an environment variable or a plaintext `~/.vibe/.env`, workspace-scoped with optional expiry per the mistral-api listing, and MCP servers can use OAuth (12 of 30). Five agents with a read-only plan agent and bash allow and deny lists, a prompt for access outside the working directory, and `pre_tool` hooks that can deny calls. The default auto-approves file edits, and there's no sandbox on the host. Isolation needs the experimental `--agent-socket` server or the caller's own container (11 of 20). Project config, hooks and MCP servers load only from trusted folders, and `-p` needs `--trust` to load them. The safety page warns that smart-approve isn't a sandbox. No network egress control on the host, and MAI-2026-003 says injected instructions could trigger the bypassed commands (8 of 15). OpenTelemetry tracing is opt-in, with default, strict and no redaction, and each run can write a session journal and an export with the effective config. Managed admin config exists, and audit logs come with the Enterprise plan (13). SECURITY.md asks for private reports, security.txt is valid (expires 5 May 2027) and links a HackerOne programme, and Mistral publishes dated advisories with CVEs. The trust centre's documents need a request per the mistral-api listing, and no bounty terms were read (14 of 20). 12+11+8+13+14 = 58.)
- Agent ergonomics, Mistral Vibe CLI +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).); Mistral Vibe CLI 84 (Framework reading, adapted to a harness driven by a pipeline. `--enabled-tools` and `--disabled-tools` with globs and regex (in `-p` the first disables everything else), per-tool and per-MCP-tool permissions, and switches for subagents and background processes (20 of 25). `--max-turns`, `--max-tokens`, `--max-price` and `--time-limit`, with text, json and streaming output and an export file with usage and cost (20). Exit codes 0 to 4 with named outcomes, refusals reported with a code, and config problems listed under `warnings` (18). `--resume SESSION_ID` and `--continue`, SIGTERM stops a run so it can be resumed, and model API failures are retried before exit 2 (16). One required input (the prompt), a GitHub Action and the ACP server, but no SDK, and the app-server's JSON-RPC protocol isn't documented for outside use (10). 20+20+18+16+10 = 84.)
- Schema & documentation, Clawboo +7: 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).); Mistral Vibe CLI 76 (Framework reading. A configuration reference with each key's type and default, the `export.json` fields, and the `--agent-socket` JSON-RPC methods with typed params and results in the README, plus ACP. No published schema file for the config or the streaming events was found (16 of 25). docs.mistral.ai/llms.txt indexes the CLI pages, each with a Markdown twin (10). The safety page says what each agent allows and when to use it, but it says `-p` falls back to `auto-approve` where the README and source say `accept-edits`, the offline guide and the configuration reference name `enable_auto_update`, which the source doesn't define (it reads `enable_update_checks`), and the API keys and offline pages carry unresolved TODO notes for developers (10 of 20). Output formats, agent names, permission values and OpenTelemetry redaction modes are enums, and the config is validated on load (12). Many examples and an exit-code table that maps each code to the outcome names in `export.json` (13). Dated changelog and version tags (15). 16+10+10+12+13+15 = 76.)