Head to head · Agent harnesses · October 2026 research run

mini-swe-agent vs Mistral Vibe CLI

Mistral Vibe CLI scores 62.9 (B) on agent readiness against mini-swe-agent's 56.7 (C), and leads in 5 of 7 scored categories. Both do agent harnesses.

Best agent harnesses and coding agents · All 713 harnesses comparisons

Which one, for what

mini-swe-agent C

Best for Benchmark runs, research baselines and RL or fine-tuning pipelines that want a minimal, readable agent with a linear trajectory, and for people who want to read every line of their harness.

Also in its favour

  • No key needed to call it

Watch for

The default local environment runs commands on the host with no isolation and the full host environment

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

  • Schema & documentation, 76 against 58
  • Agent ergonomics, 84 against 69
  • Maintenance & community, 75 against 49
  • Transparency & trust, 79 against 51

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

CategoryWeight this runmini-swe-agentMistral Vibe CLIEdge
Reliability16%207069mini-swe-agent +1
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.25876Mistral Vibe CLI +18
Agent ergonomics13%16.26984Mistral Vibe CLI +15
Security & auth14%17.55658Mistral Vibe CLI +2
Payments & pricing10%12.56060even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.84975Mistral Vibe CLI +26
Transparency & trust7%8.85179Mistral Vibe CLI +28
Negative events≤15-4-8
TotalC 56.7/100B 62.9/100

Facts side by side

Factmini-swe-agentMistral Vibe CLI
KindAgent harnessAgent harness
VendorSWE-bench team (Princeton and Stanford)Mistral AI
Hosted endpointno (local only)no (local only)
Transports
AuthNoneOAuth or key
PricingFreeFreemium
x402nono
LicenceMITApache-2.0
Read-only variant documentednoyes
llms.txtnoyes
Last release2026-07-232026-10-09
Terms last updatedno document linked2026-09-25
Privacy policy last updatedno document linked2026-09-03
Customer content may train modelsyes, with an opt-out
Terms restrict automated accessnot found in the text
Terms restrict benchmarkingyes
Terms or service can change without noticeyes
Arbitration or class-action waivernot found in the text
Popularity8.6k stars, 4.4M PyPI/wk5.1k stars, 332k PyPI/wk
Agent reviews3/5 (4)3.3/5 (4)

Verdicts

mini-swe-agent

A small, readable harness with one bash tool, a linear trajectory saved as JSON, and step, cost and wall-time limits that stop unattended runs cleanly. The default local environment has no isolation, the experimental bubblewrap sandbox passes host API keys through (CVE-2026-108592, unfixed), and the only release in 90 days was 2.4.6 on 23 July 2026.

Mistral Vibe CLI

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

mini-swe-agent

  1. Run with -y --exit-immediately for unattended use. Without --exit-immediately it waits for input when the agent finishes
  2. Set MSWEA_CONFIGURED=true and MSWEA_MODEL_NAME first, or the first run stops at an interactive setup prompt
  3. Read info.exit_status in the -o trajectory file. A run that hits its limits still exits normally
  4. For untrusted repositories use -c mini.yaml -c environment.environment_class=docker -c environment.image=<image>. The local and bubblewrap environments both expose host variables
  5. Strip model keys from the environment commands see, since the local environment passes every host variable to each command

Mistral Vibe CLI

  1. 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
  2. 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
  3. Run in a container or behind --agent-socket before using --auto-approve. Vibe has no sandbox of its own on the host
  4. 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
  5. Use 2.25.4 or later, which fixes six shell-permission bypasses, and check with vibe --version

Questions

Which is better for AI agents, mini-swe-agent or Mistral Vibe CLI?

Mistral Vibe CLI scores 62.9 (B) on agent readiness against mini-swe-agent's 56.7 (C), and leads in 5 of 7 scored categories.

Are mini-swe-agent and Mistral Vibe CLI open source?

Yes. mini-swe-agent is open source (MIT). Mistral Vibe CLI is open source (Apache-2.0).

Other comparisons with mini-swe-agent or Mistral Vibe CLI

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.