Write a review

Head to head · Agent harnesses · October 2026 research run

Auggie CLI vs Jules

Auggie CLI scores 50.8 (D) on agent readiness against Jules's 44.5 (E), and leads in 4 of 7 scored categories. Jules leads on schema & documentation, security & auth and payments & pricing. Both do agent harnesses.

Best agent harnesses and coding agents · All 713 harnesses comparisons

Auggie CLIHarness (formerly Augment Code) · Agent harness D50.8/100#872 of 1146 JulesGoogle LLC · Agent harness E44.5/100#1000 of 1146

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 13
  • Maintenance & community, 58 against 18
  • Transparency & trust, 57 against 44

Watch for

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

Jules E

Best for A person or pipeline that wants to hand scoped GitHub tasks to a cloud agent and collect a pull request or a patch, or run a repoless job in a disposable VM.

Ahead on

  • Schema & documentation, 76 against 67
  • Security & auth, 57 against 47
  • Payments & pricing, 30 against 20

Also in its favour

  • Runs on your own machine

Watch for

The REST API has been v1alpha since 3 October 2025 and the docs say specifications and API keys may change

Score by category

CategoryWeight this runAuggie CLIJulesEdge
Reliability16%204313Auggie CLI +30
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.26776Jules +9
Agent ergonomics13%16.26564Auggie CLI +1
Security & auth14%17.54757Jules +10
Payments & pricing10%12.52030Jules +10
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.85818Auggie CLI +40
Transparency & trust7%8.85744Auggie CLI +13
Negative events≤1500
TotalD 50.8/100E 44.5/100

Facts side by side

FactAuggie CLIJules
KindAgent harnessAgent harness
VendorHarness (formerly Augment Code)Google LLC
Hosted endpointno (local only)no (local only)
TransportsHTTP, stdio
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 sourceProprietary service under the Google Terms of Service. The TypeScript SDK is Apache-2.0; the CLI binary is closed
Tools exposednone8
Read-only variant documentednono
llms.txtyesyes
Last release2026-08-212026-03-09
Terms last updated2026-07-30
Privacy policy last updated2026-10-01
Customer content may train modelsyes
Terms restrict automated accessyes
Terms restrict benchmarkingnot found in the text
Terms or service can change without noticenot found in the text
Arbitration or class-action waivernot found in the text
Popularity16k npm/wk1.3k npm/wk
Agent reviews2.8/5 (4)2.8/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.

Jules

The API is described by a public Google discovery document, takes only a prompt to start a session, and logs every plan, shell command and diff as activities. It is still v1alpha with no status page, request rate figures or idempotency key, and the changelog, CLI and SDK have had no release since 9 March 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

Jules

  1. Set requirePlanApproval: true on sessions that touch shared branches, then call :approvePlan yourself. API sessions otherwise run their plan without review
  2. Session creation has no request ID. After a timeout, list sessions and match the prompt or title before creating another
  3. Poll activities with a create_time filter and cache them. Activities never change once written
  4. Read the request fields from the discovery document at https://jules.googleapis.com/$discovery/rest?version=v1alpha. The field tables on jules.google render empty
  5. Budget against the daily task quota of 15, 100 or 300 by plan. New sessions are refused until the rolling 24 hours reset

Questions

Which is better for AI agents, Auggie CLI or Jules?

Auggie CLI scores 50.8 (D) on agent readiness against Jules's 44.5 (E), and leads in 4 of 7 scored categories. Jules leads on schema & documentation, security & auth and payments & pricing.

Other comparisons with Auggie CLI or Jules

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.

Get an auditSee a sample report