GILD verdict
Choose Auggie CLI when your agents lose most of their turns finding the right code in a large codebase and you want one agent everywhere: the terminal, CI and the IDE.
Hold a team commitment until Harness puts in writing what happens to your plan, contract and data.
Auggie CLI
AI Coding Agent by Harness
+59 Strong positiveFit and limits
Who it fits
- Agents waste turns searching for the code that matters in a large or legacy codebase split across services.
- Engineers want to keep their editors. The agent runs in VS Code, JetBrains IDEs, Zed, Neovim, Emacs, and the terminal.
- You want one bill for models from Anthropic, OpenAI, Google, xAI, and others, or for routing through Augment's Prism router.
- You plan to run the agent headless in CI for review, triage, or failure summaries, with service accounts for the automation.
Where it falls short
- Standard and Business plans have no per-user budgets. Budgets and organization usage dashboards are Enterprise-only, and usage past the plan continues pay as you go.
- The Context Engine uploads your code to Augment's cloud to index it. Some security reviews reject that upload.
- Auggie CLI and Cosmos cloud agents enforce tool permission rules, and the IDE extension ignores them. One engineer can run with different guardrails in the terminal and in the IDE.
- Completions and Next Edit left non-Enterprise plans on March 31, 2026. Pricing has changed three times since May 2025, so check the date on any review or quote you read.
Implementation reality
Decide what the index may see
Indexing uploads every file in the workspace except those matched by .gitignore or .augmentignore. Write an .augmentignore before the first engineer opens the repository, and have security approve the upload. Augment states it never trains on customer code and protects code privacy with a proof-of-possession API.
Put a ceiling on usage
Standard at US$20 per month and Business at US$100 per month include that amount of usage, pooled across up to 50 seats. Tokens bill at the model's list price plus a 40% service fee, and usage beyond the plan continues automatically. Agree a model policy, and read per-member usage on the web dashboard each week.
Write permission rules into the repository
Commit a .augment/settings.json with toolPermissions so every CLI session and Cosmos agent in the repository follows the same allow and deny rules. When policies conflict, the most restrictive rule wins. Decide which surface handles risky work, since the IDE extension skips these rules.
Write the rules the agent reads
Auggie reads AGENTS.md, CLAUDE.md, .augment-guidelines, and Markdown rules in .augment/rules, so one versioned file can serve Auggie and other agents. Teams that report steady results keep these files short and review them like code.
Plan for the ownership change
Harness announced on October 8, 2026 that it acquired Cosmos, Auggie CLI, the Code Context Engine, and related technology, and that the team behind them joins Harness. Harness is folding Cosmos into its Harness Cosmos Software Factory Agent and says customers can adopt it, continue using their preferred coding tools, or use both. Neither Harness's announcement nor Augment's says anything about Auggie CLI plans, prices or the IDE extensions. Ask which entity holds your contract and data, and get plan terms in writing.
What to measure in your pilot
- GILD read both deal announcements and found no new Auggie CLI pricing; rerun your cost comparison at renewal if the 40% service fee or the 50-seat flat plan changes.
- Augment's v2 harness was still a GitHub prerelease on October 19, 2026; run v1 and v2 on 20 of your own tickets and keep v2 only if dollars per accepted change fall.
- GILD found no public account of a whole team sharing one Standard or Business pool; log weekly spend per member for a month, and buy Enterprise budgets if one engineer uses half.
Sources
- Official documentation
- 19
- Public source
- 1
- Augment Code pricing
- Augment docs: Token-based pricing
- Augment docs: Available models
- Augment docs: Introducing Auggie CLI
- Augment docs: Install Auggie CLI
- Augment docs: ACP clients
- Augment docs: Install Augment for Visual Studio Code
- Augment docs: Install Augment for JetBrains IDEs
- Augment docs: Index your workspace (CLI)
- Augment Code security & privacy
- Augment docs: Tool permissions
- Augment docs: Rules & guidelines
- Augment docs: Using Auggie with automation
- Augment docs: Service accounts
- Augment docs: Usage dashboards & budgets
- Augment docs: Completions
- Augment blog: Rebuilding the Auggie CLI harness (Aug 14, 2026)
- Augment blog: Augment Code's next chapter (Oct 8, 2026)
- Harness blog: Harness acquires Augment Code (Oct 8, 2026)
- GitHub: Release auggie-v2 v1.2.0-prerelease.202610191517 (Oct 19, 2026)