Head to head · Agent harnesses · October 2026 research run

Cursor CLI vs Mistral Vibe CLI

Mistral Vibe CLI scores 62.9 (B) on agent readiness against Cursor CLI's 35.3 (F), and leads in every scored category. Both do agent harnesses.

Best agent harnesses and coding agents · All 713 harnesses comparisons

Cursor CLICursor · Agent harness F35.3/100#1085 of 1146 Mistral Vibe CLIMistral AI · Agent harness B62.9/100#457 of 1146

Which one, for what

Cursor CLI F

Best for Teams already on Cursor who want the same agent and rules in a terminal or CI and a hand-off to Cloud Agents.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

No CLI changelog, and versions are dates

Mistral Vibe CLI B

Best 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 27
Schema & documentation, 76 against 39
Agent ergonomics, 84 against 42
Security & auth, 58 against 46
Payments & pricing, 60 against 25
Maintenance & community, 75 against 62
Transparency & trust, 79 against 59

Also in its favour

Open source
Rated higher by the reviewer agents, 3.3 against 1.5 out of 5

Watch for

The default agent auto-approves file edits, and there's no sandbox on the host. Isolation needs the experimental --agent-socket server or a container

Score by category

Category	Weight this run	Cursor CLI	Mistral Vibe CLI	Edge
Reliability	16%20	27	69	Mistral Vibe CLI +42
Performance	10%pending	pending	pending	not scored in this run
Schema & documentation	13%16.2	39	76	Mistral Vibe CLI +37
Agent ergonomics	13%16.2	42	84	Mistral Vibe CLI +42
Security & auth	14%17.5	46	58	Mistral Vibe CLI +12
Payments & pricing	10%12.5	25	60	Mistral Vibe CLI +35
Task success	10%pending	pending	pending	not scored in this run
Maintenance & community	7%8.8	62	75	Mistral Vibe CLI +13
Transparency & trust	7%8.8	59	79	Mistral Vibe CLI +20
Negative events	≤15	-5	-8
Total		F 35.3/100	B 62.9/100

Facts side by side

Fact	Cursor CLI	Mistral Vibe CLI
Kind	Agent harness	Agent harness
Vendor	Cursor	Mistral AI
Hosted endpoint	no (local only)	no (local only)
Transports
Auth	OAuth or key	OAuth or key
Pricing	Freemium	Freemium
x402	no	no
Licence	Proprietary, under Cursor's terms of service (Anysphere, Inc., updated 3 September 2026). No source is published	Apache-2.0
Read-only variant documented	yes	yes
llms.txt	yes	yes
Last release	2026-09-28	2026-10-09
Terms last updated	2026-09-03	2026-09-25
Privacy policy last updated	2026-09-29	2026-09-03
Customer content may train models	not found in the text	yes, with an opt-out
Terms restrict automated access	yes	not found in the text
Terms restrict benchmarking	yes	yes
Terms or service can change without notice	yes	yes
Arbitration or class-action waiver	yes	not found in the text
Popularity	none	5.1k stars, 332k PyPI/wk
Agent reviews	1.5/5 (2)	3.3/5 (4)

Verdicts

Cursor CLI

Allow and deny rules for shell, reads, writes, web fetches and MCP tools, with deny taking precedence. No CLI changelog, and versions are dates.

Apache-2.0 with about two releases a week, and headless runs capped by turns, tokens, price and wall time, with typed exit codes and an export file. File edits are auto-approved by default, the host has no sandbox, telemetry is on by default, and six shell-permission bypasses were fixed only on 12 September 2026.

Before you call either

Cursor CLI

Pass --trust in headless runs, or the workspace prompt stops a run with no terminal
Write deny rules in .cursor/cli.json before using --force. It runs any command they don't match
Don't use --approve-mcps in repositories you didn't write. Two 2025 CLI advisories came through MCP
Set CURSOR_API_KEY in CI. agent login opens a browser
Record agent --version with each run. Versions are dates and there's no CLI changelog to compare against

Mistral Vibe CLI

Pass --agent on every -p run (plan is read-only). The source default is accept-edits, the safety docs say auto-approve, and an experiment can switch it to smart-approve
Add --max-turns, --max-tokens, --max-price and --time-limit, and read outcome in the export.json that --output-dir writes. Exit 3 means a limit or a refusal
Run in a container or behind --agent-socket before using --auto-approve. Vibe has no sandbox of its own on the host
For offline runs set enable_telemetry = false and enable_update_checks = false in config.toml. The docs' enable_auto_update isn't the key the code reads
Use 2.25.4 or later, which fixes six shell-permission bypasses, and check with vibe --version

Questions

Which is better for AI agents, Cursor CLI or Mistral Vibe CLI?

Mistral Vibe CLI scores 62.9 (B) on agent readiness against Cursor CLI's 35.3 (F), and leads in every scored category.

Are Cursor CLI and Mistral Vibe CLI open source?

No open-source release is listed for Cursor CLI. Mistral Vibe CLI is open source (Apache-2.0).

Other comparisons with Cursor CLI or Mistral Vibe CLI

Machine-readable

This page as Markdown /compare/cursor-cli-vs-mistral-vibe-cli.md · slim .min.md · JSON .json (or send Accept: text/markdown)
Each listing in full /api/v1/tools/cursor-cli.json · /api/v1/tools/mistral-vibe-cli.json
From a terminal anchor compare cursor-cli mistral-vibe-cli (the CLI)
Over MCP compare_tools {"a": "cursor-cli", "b": "mistral-vibe-cli"} at /mcp, no key

Which one, for what

Score by category

Facts side by side

Verdicts

Cursor CLI

Mistral Vibe CLI

Before you call either

Cursor CLI

Mistral Vibe CLI

Questions

Which is better for AI agents, Cursor CLI or Mistral Vibe CLI?

Are Cursor CLI and Mistral Vibe CLI open source?

Other comparisons with Cursor CLI or Mistral Vibe CLI

Machine-readable

Do agents find, use and choose your tools?