Write a review

Head to head · Agent harnesses · October 2026 research run

Auggie CLI vs Kimi Code CLI

Kimi Code CLI scores 62.1 (B) on agent readiness against Auggie CLI's 50.8 (D), and leads in 6 of 7 scored categories. 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 Kimi Code CLIMoonshot AI · Agent harness B62.1/100#492 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.

Also in its favour

  • No incidents deducted, where Kimi Code CLI loses 4 points for them

Watch for

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

Kimi Code CLI B

Best for Developers on Kimi models who want a terminal agent with ACP and a local REST API, or an open-source harness that also runs Claude, GPT or Gemini models.

Ahead on

  • Reliability, 68 against 43
  • Schema & documentation, 85 against 67
  • Agent ergonomics, 71 against 65
  • Payments & pricing, 60 against 20
  • Maintenance & community, 72 against 58
  • Transparency & trust, 62 against 57

Also in its favour

  • Free to start without a card
  • Open source

Watch for

Print mode approves every tool call under Never Ask, where the dangerous-command guard is off

Score by category

CategoryWeight this runAuggie CLIKimi Code CLIEdge
Reliability16%204368Kimi Code CLI +25
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.26785Kimi Code CLI +18
Agent ergonomics13%16.26571Kimi Code CLI +6
Security & auth14%17.54745Auggie CLI +2
Payments & pricing10%12.52060Kimi Code CLI +40
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.85872Kimi Code CLI +14
Transparency & trust7%8.85762Kimi Code CLI +5
Negative events≤150-4
TotalD 50.8/100B 62.1/100

Facts side by side

FactAuggie CLIKimi Code CLI
KindAgent harnessAgent harness
VendorHarness (formerly Augment Code)Moonshot AI
Hosted endpointno (local only)no (local only)
Transports
AuthOAuth or keyOAuth or key
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.txtyesyes
Last release2026-08-212026-10-14
Terms last updated
Privacy policy last updated
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/wk37k npm/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.

Kimi Code CLI

MIT-licensed, with 32 releases in the 90 days to 14 October 2026, kimi -p with stream-json output, an ACP server and a local REST API with a live OpenAPI document. Print mode approves every tool call except static deny rules, no sandbox is documented, and telemetry is on by default without a list of what it sends.

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

Kimi Code CLI

  1. kimi -p approves every tool call. Add [[permission.rules]] deny entries and run it in a container, since no sandbox is documented
  2. Set KIMI_LOOP_MAX_STEPS_PER_TURN for unattended runs. Steps per turn are unlimited by default
  3. Pass the model with KIMI_MODEL_NAME, KIMI_MODEL_API_KEY and KIMI_MODEL_PROVIDER_TYPE. OPENAI_API_KEY or ANTHROPIC_API_KEY in the shell is ignored otherwise
  4. Set KIMI_DISABLE_TELEMETRY=1 and use 0.41.0 or later, since earlier print-mode runs ignored it
  5. Install @moonshot-ai/kimi-code or the kimi-code formula. The kimi-cli and kimi-code packages on PyPI are the archived Python CLI

Questions

Which is better for AI agents, Auggie CLI or Kimi Code CLI?

Kimi Code CLI scores 62.1 (B) on agent readiness against Auggie CLI's 50.8 (D), and leads in 6 of 7 scored categories.

Are Auggie CLI and Kimi Code CLI open source?

No open-source release is listed for Auggie CLI. Kimi Code CLI is open source (MIT).

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

Get an auditSee a sample report