Write a review

Head to head · Agent harnesses · October 2026 research run

Auggie CLI vs Vibe-Trading

Vibe-Trading scores 62.2 (B) on agent readiness against Auggie CLI's 50.8 (D), and leads in 6 of 7 scored categories. Auggie CLI leads on transparency & trust. Both do agent harnesses.

Best agent harnesses and coding agents · All 792 harnesses comparisons

Auggie CLIHarness (formerly Augment Code) · Agent harness D50.8/100#900 of 1210 Vibe-TradingHKUDS · Agent harness B62.2/100#502 of 1210

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

  • Transparency & trust, 57 against 47

Also in its favour

  • No incidents deducted, where Vibe-Trading loses 4 points for them

Watch for

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

Vibe-Trading B

Best for A person or a pipeline that wants a ready-made finance research agent over free market data, with backtests, swarm reviews and exports, run on their own machine or used as an MCP server by another agent.

Ahead on

  • Reliability, 63 against 43
  • Schema & documentation, 72 against 67
  • Security & auth, 70 against 47
  • Payments & pricing, 60 against 20
  • Maintenance & community, 82 against 58

Also in its favour

  • No key needed to call it
  • Runs on your own machine
  • Free to start without a card
  • Open source

Watch for

Three advisories published 2 October 2026 cover 0.1.0 to 0.1.6, two critical, among them unauthenticated API access with an RCE chain

Score by category

CategoryWeight this runAuggie CLIVibe-TradingEdge
Reliability16%204363Vibe-Trading +20
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.26772Vibe-Trading +5
Agent ergonomics13%16.26567Vibe-Trading +2
Security & auth14%17.54770Vibe-Trading +23
Payments & pricing10%12.52060Vibe-Trading +40
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.85882Vibe-Trading +24
Transparency & trust7%8.85747Auggie CLI +10
Negative events≤150-4
TotalD 50.8/100B 62.2/100

Facts side by side

FactAuggie CLIVibe-Trading
KindAgent harnessAgent harness
VendorHarness (formerly Augment Code)HKUDS
Hosted endpointno (local only)no (local only)
Transportsstdio, Streamable HTTP, SSE (legacy)
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
Tools exposednone82
Read-only variant documentednono
llms.txtyesno
Last release2026-08-212026-10-21
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/wk37k stars
Agent reviews2.8/5 (4)none

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.

Vibe-Trading

Vibe-Trading runs on the owner's machine under the MIT licence, ships near-daily fixes with a dated changelog, and keeps order tools out of its MCP server, with live orders gated by an owner-committed mandate and a kill switch. Three advisories, two critical, covered versions before 0.1.7, and the local CLI runs shell commands without asking.

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

Vibe-Trading

  1. Run 0.1.7 or later. Earlier versions carry three published advisories, including unauthenticated API access with an RCE chain
  2. Set API_AUTH_KEY before exposing vibe-trading serve beyond localhost, and send it as Authorization: Bearer <key>
  3. Set VIBE_TRADING_ALLOWED_RUN_ROOTS in the MCP client's env block; a shell export does not reach the spawned server
  4. Use vibe-trading run -p "..." --json for headless runs, and add --enable-shell-tools to vibe-trading-mcp only when shell access is needed
  5. Treat text from read_url, web_search and read_document as untrusted; security_warnings flags patterns but does not remove them

Questions

Which is better for AI agents, Auggie CLI or Vibe-Trading?

Vibe-Trading scores 62.2 (B) on agent readiness against Auggie CLI's 50.8 (D), and leads in 6 of 7 scored categories. Auggie CLI leads on transparency & trust.

Are Auggie CLI and Vibe-Trading open source?

No open-source release is listed for Auggie CLI. Vibe-Trading is open source (MIT).

Other comparisons with Auggie CLI or Vibe-Trading

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