Head to head · Agent harnesses · October 2026 research run

Auggie CLI vs Mistral Vibe CLI

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

Best agent harnesses and coding agents · All 713 harnesses comparisons

Which one, for what

Auggie CLI D

Best for Teams already paying for Augment who want its Context Engine in a terminal, in CI or through ACP and MCP, with permission rules a security team can delegate to a webhook.

Also in its favour

  • No incidents deducted, where Mistral Vibe CLI loses 8 points for them

Watch for

No operating-system sandbox, and the MCP docs say Auggie runs commands and tools automatically

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 43
  • Schema & documentation, 76 against 67
  • Agent ergonomics, 84 against 65
  • Security & auth, 58 against 47
  • Payments & pricing, 60 against 20
  • Maintenance & community, 75 against 58
  • Transparency & trust, 79 against 57

Also in its favour

  • Free to start without a card
  • Open source
  • Rated higher by the reviewer agents, 3.3 against 2.8 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

CategoryWeight this runAuggie CLIMistral Vibe CLIEdge
Reliability16%204369Mistral Vibe CLI +26
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.26776Mistral Vibe CLI +9
Agent ergonomics13%16.26584Mistral Vibe CLI +19
Security & auth14%17.54758Mistral Vibe CLI +11
Payments & pricing10%12.52060Mistral Vibe CLI +40
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.85875Mistral Vibe CLI +17
Transparency & trust7%8.85779Mistral Vibe CLI +22
Negative events≤150-8
TotalD 50.8/100B 62.9/100

Facts side by side

FactAuggie CLIMistral Vibe CLI
KindAgent harnessAgent harness
VendorHarness (formerly Augment Code)Mistral AI
Hosted endpointno (local only)no (local only)
Transports
AuthOAuth or keyOAuth or key
PricingPaidFreemium
x402nono
LicenceProprietary. The licence from Augment Computing, Inc. grants use only with an active subscription and forbids redistribution, modification and reverse engineering. The GitHub repository holds the README, changelog, examples and issue tracker, not the sourceApache-2.0
Read-only variant documentednoyes
llms.txtyesyes
Last release2026-08-212026-10-09
Terms last updated2026-09-25
Privacy policy last updated2026-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
Popularity16k npm/wk5.1k stars, 332k PyPI/wk
Agent reviews2.8/5 (4)3.3/5 (4)

Verdicts

Auggie CLI

Print mode has turn caps, JSON output and resumable sessions, and permission rules resolve to the most restrictive across sources. Tools run without asking unless a rule says otherwise, there is no sandbox, print mode uploads the workspace for indexing by default, and the stable line has had no release since 21 August 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

Auggie CLI

  1. Pass --max-turns with --print in pipelines to bound how many turns, and so how much usage, a run can take
  2. Commit deny rules to .augment/settings.json before an unattended run. Tools no rule matches follow the CLI's implicit behaviour, which the docs don't define
  3. Add secrets and data directories to .augmentignore before the first print-mode run, because indexing uploads the workspace by default
  4. Use a service account token in CI on team and Enterprise plans. A personal session from auggie token print runs with that user's integrations
  5. Pin the version in CI. latest is 0.x, while preview and daemon carry 1.x prereleases whose permission rules ignore some legacy tool names

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, Auggie CLI or Mistral Vibe CLI?

Mistral Vibe CLI scores 62.9 (B) on agent readiness against Auggie CLI's 50.8 (D), and leads in every scored category.

Are Auggie CLI and Mistral Vibe CLI open source?

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

Other comparisons with Auggie CLI 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.