Head to head · Agent harnesses · October 2026 research run

Auggie CLI vs Harness²

Auggie CLI scores 50.8 (D) on agent readiness against Harness²'s 41.6 (E), and leads in 6 of 7 scored categories. Harness² leads on payments & pricing. 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

  • Reliability, 43 against 20
  • Schema & documentation, 67 against 51
  • Agent ergonomics, 65 against 59
  • Maintenance & community, 58 against 36
  • Transparency & trust, 57 against 44

Watch for

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

Harness² E

Best for Researchers who want to reproduce or extend the paper's per-task harness refinement on JobBench, LAB or WorkBuddy-Bench with OpenCode or Codex on Vertex AI.

Ahead on

  • Payments & pricing, 40 against 20

Also in its favour

  • No key needed to call it
  • Open source

Watch for

No hosted API, MCP server or tagged release. It installs from a source checkout only, and harness2 isn't on PyPI

Score by category

CategoryWeight this runAuggie CLIHarness²Edge
Reliability16%204320Auggie CLI +23
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.26751Auggie CLI +16
Agent ergonomics13%16.26559Auggie CLI +6
Security & auth14%17.54744Auggie CLI +3
Payments & pricing10%12.52040Harness² +20
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.85836Auggie CLI +22
Transparency & trust7%8.85744Auggie CLI +13
Negative events≤1500
TotalD 50.8/100E 41.6/100

Facts side by side

FactAuggie CLIHarness²
KindAgent harnessAgent harness
VendorHarness (formerly Augment Code)Google (Google Research)
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 sourceApache-2.0. Bundled benchmark runners keep their upstream licences (Apache-2.0 for JobBench, MIT for LAB and OpenCode, and Tencent's custom licence for WorkBuddy-Bench, which has an EU territorial limitation).
Read-only variant documentednono
llms.txtyesno
Last release2026-08-212026-10-08
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/wk4.2k stars
Agent reviews2.8/5 (4)2.5/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.

Harness²

Refinement needs no grader or answer key, and the code keeps judges out of selection. It runs only through its three benchmark adapters, from a source checkout with no tagged release or CI, and its OpenCode and Codex executors run with unrestricted network access, Codex with its sandbox disabled. The benchmark gains are the authors' claims.

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

Harness²

  1. Don't plan to call Harness² as a service. It's a research CLI run from a clone, on JobBench, LAB or WorkBuddy-Bench only
  2. Ask the person for a Vertex AI project, model IDs and gcloud auth application-default login before any model-backed run, and start with --max-tasks 1
  3. Run executors behind an egress firewall and block huggingface.co and github.com after setup, as the docs advise, so rubrics can't be fetched
  4. Write .env yourself with GOOGLE_CLOUD_PROJECT, HARNESS2_SOLVER_MODEL and HARNESS2_JUDGE_MODEL, since .env.example isn't shipped, and never commit it
  5. Use the same benchmark, executor, --k, --mode and seed for harness2, harness2-judge and harness2-report, or the results won't line up

Questions

Which is better for AI agents, Auggie CLI or Harness²?

Auggie CLI scores 50.8 (D) on agent readiness against Harness²'s 41.6 (E), and leads in 6 of 7 scored categories. Harness² leads on payments & pricing.

Are Auggie CLI and Harness² open source?

No open-source release is listed for Auggie CLI. Harness² is open source (Apache-2.0. Bundled benchmark runners keep their upstream licences (Apache-2.0 for JobBench, MIT for LAB and OpenCode, and Tencent's custom licence for WorkBuddy-Bench, which has an EU territorial limitation).).

Other comparisons with Auggie CLI or Harness²

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.