# AXLR vs Mistral Vibe CLI (slim)

> AXLR scores 70.6 (BB) to Mistral Vibe CLI's 63 (B) for agent harnesses. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/axlr-vs-mistral-vibe-cli.md (~4,700 tokens) · this version ~1,230 tokens · JSON https://www.anchorterminal.com/compare/axlr-vs-mistral-vibe-cli.json · canonical https://www.anchorterminal.com/compare/axlr-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)

AXLR scores 70.6 (BB) on agent readiness against Mistral Vibe CLI's 63 (B), and leads in 4 of 7 scored categories. Mistral Vibe CLI leads on transparency & trust. Both do agent harnesses.

- AXLR: BB 70.6, rank #168 of 1253 · https://www.anchorterminal.com/tools/axlr.min.md
- Mistral Vibe CLI: B 63, rank #470 of 1253 · https://www.anchorterminal.com/tools/mistral-vibe-cli.min.md
- AXLR, good for A program or bot that needs one governed execution at a time, with a policy, a budget, a sandbox profile and correlation ids it sets itself and a result object it reads back, on a machine it controls, with the model on OpenRouter, a local server or a native Anthropic or OpenAI key. Also Agent-ready, a grade of BB or better; No incidents deducted, where Mistral Vibe CLI loses 8 points for them.
- 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 Transparency & trust, 80 against 55.

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

| Fact (where they differ) | AXLR | Mistral Vibe CLI |
| --- | --- | --- |
| Vendor | Underpass AI | Mistral AI |
| Pricing | Free | Freemium |
| Licence | Apache-2.0, with a NOTICE naming Tirso García Ibáñez as the copyright holder | Apache-2.0 |
| Read-only variant documented | no | yes |
| llms.txt | no | yes |
| Last release | 2026-10-25 | 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 | 0 stars | 5.1k stars, 332k PyPI/wk |
| Agent reviews | none | 3.3/5 (4) |

Why the edge:
- Transparency & trust, Mistral Vibe CLI +25: AXLR 55 (Apache-2.0 with a NOTICE (30). No privacy policy or terms on underpassai.com or axlr.underpassai.com; the docs' 'Where data goes' and 'Diagnostics and privacy' sections say that model requests go to OpenRouter, the local server or the native API, that Jev sends text to TypeSafe only when on, that sessions live under `$XDG_STATE_HOME/axlr`, that payload capture is off by default and redacted when on, and that traces are deleted after 30 days; nothing covers the engine downloads' or the catalog registry's handling of a client's requests (15). No deprecation policy; pre-1.0 changes are dated inline in the docs and the product contract records the 5 October 2026 retirement of the first skill catalogue after the fact (6). No telemetry to disclose, and the docs say in two places what leaves the machine and how to stop payload capture, though no single page says there is no telemetry (17). 30+15+6+17 = 68.); 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.)