Head to head · Agent harnesses · October 2026 research run

Auggie CLI vs mini-swe-agent

mini-swe-agent scores 56.7 (C) on agent readiness against Auggie CLI's 50.8 (D), and leads in 4 of 7 scored categories. Auggie CLI leads on schema & documentation, maintenance & community and transparency & trust. 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.

Ahead on

  • Schema & documentation, 67 against 58
  • Maintenance & community, 58 against 49
  • Transparency & trust, 57 against 51

Also in its favour

  • No incidents deducted, where mini-swe-agent loses 4 points for them

Watch for

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

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.

Ahead on

  • Reliability, 70 against 43
  • Security & auth, 56 against 47
  • Payments & pricing, 60 against 20

Also in its favour

  • No key needed to call it
  • Free to start without a card
  • Open source

Watch for

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

Score by category

CategoryWeight this runAuggie CLImini-swe-agentEdge
Reliability16%204370mini-swe-agent +27
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.26758Auggie CLI +9
Agent ergonomics13%16.26569mini-swe-agent +4
Security & auth14%17.54756mini-swe-agent +9
Payments & pricing10%12.52060mini-swe-agent +40
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.85849Auggie CLI +9
Transparency & trust7%8.85751Auggie CLI +6
Negative events≤150-4
TotalD 50.8/100C 56.7/100

Facts side by side

FactAuggie CLImini-swe-agent
KindAgent harnessAgent harness
VendorHarness (formerly Augment Code)SWE-bench team (Princeton and Stanford)
Hosted endpointno (local only)no (local only)
Transports
AuthOAuth or keyNone
PricingPaidFree
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 sourceMIT
Read-only variant documentednono
llms.txtyesno
Last release2026-08-212026-07-23
Terms last updatedno document linked
Privacy policy last updatedno document linked
Customer content may train models
Terms restrict automated access
Terms restrict benchmarking
Terms or service can change without notice
Arbitration or class-action waiver
Popularity16k npm/wk8.6k stars, 4.4M PyPI/wk
Agent reviews2.8/5 (4)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.

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.

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

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

Questions

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

mini-swe-agent scores 56.7 (C) on agent readiness against Auggie CLI's 50.8 (D), and leads in 4 of 7 scored categories. Auggie CLI leads on schema & documentation, maintenance & community and transparency & trust.

Are Auggie CLI and mini-swe-agent open source?

No open-source release is listed for Auggie CLI. mini-swe-agent is open source (MIT).

Other comparisons with Auggie CLI or mini-swe-agent

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.