Key findings
- 24 of the 25 accounts that discuss the Context Engine praise it, often on large or multi-repository codebases.
- All 9 accounts that discuss speed and reliability raise timeouts, crashes, hangs, or heavy re-indexing.
- Pricing comes up in 12 accounts and 7 raise it as a concern. Several authors left after the October 2025 move to credits.
- Of the 15 accounts that compare tools or describe a price change, 7 kept Augment as the main agent and 8 moved, most often to Claude Code.
Engineers who stay on Augment stay for the Context Engine, and the ones who leave cite slow or unstable sessions and repeated repricing. GILD read public accounts published from February 6, 2025 to September 17, 2026. Nineteen of them speak for a team or organization, so a leader weighing a rollout should read those first.
Who wrote these accounts
The accounts are 49 community posts: 40 Hacker News comments, 8 GitHub issues and issue comments, and 1 Product Hunt reply. The rest are 11 blog posts and reviews, 1 independent benchmark, and 6 videos and recorded sessions. Each names its author and links its page. GILD recorded the plan, model, or client wherever the author states one.
48 come from individual builders. Of the 19 team accounts, 11 come from professional teams, among them a GitKraken engineer embedding Auggie CLI in the company's Kepler product and two Tilt engineers. Four come from small groups. Two are from one member of a team of four, one from the VP of Engineering at the consultancy Level 12, and one from the academic authors of the ProjDevBench benchmark. Four come from technical leaders: one from a CTO setting tool policy for about 220 engineers, two from Webflow's CTO, who gives every engineer Augment Code beside Cursor, and a second post from Level 12's VP of Engineering, on a client project. Augment Code co-produced two of the team accounts, both LeadDev sessions, and one newsletter discloses Augment as a sponsor.
What still applies in October 2026
Augment billed by user message from May 2025, by credits from October 20, 2025, and in dollars at model list price plus a 40% service fee from June 2026. Dollar billing arrived on a flat Business plan, and a Standard plan joined it in September 2026. Completions and Next Edit left non-Enterprise plans on March 31, 2026.
19 accounts rest on something Augment has since changed: a retired plan, the retired completions features, Remote Agents before Cosmos, or an early CLI version. Recheck those before you act on them. 34 accounts from 2025 and one from 2026 still apply as written because they describe the Context Engine, workflow, or review practice, and 13 published in 2026 are current.
Where teams put it to work
Tilt runs Auggie CLI in an Azure pipeline as a pull request review bot, with rules its engineers own, and LeadDev's session credits the bot with faster code review across time zones. Collectors ran phased trials on production work and has begun shifting to Augment as its main tool, crediting its context awareness. Cyoda's team works in small, checkpointed tasks with written guidelines and memories, and reviews generated tests like production code.
Some team accounts are warnings. One engineer's colleague got confidently invented behavior from Augment even with the feature's full source code indexed. A team of four that adopted Auggie CLI later moved to Claude Code.
- Write an .augmentignore and a rules file before the first session.
- Set a model policy and read usage weekly, since budgets are Enterprise-only.
- Keep a human reviewer and a rollback point on every agent change.
What to test in a pilot
Run the pilot on your largest repository, where engineers say the index matters most. Measure accepted changes, review time, and spend per accepted change against another agent on the same work. Record whether each engineer works in the IDE extension or the CLI, since only the CLI enforces tool permission rules.
Methodology
GILD collected public accounts through the Hacker News Algolia API, YouTube, Product Hunt, GitHub issues on augmentcode/auggie, and web searches for named engineering blogs, and opened every page on October 12, 2026. On October 25, 2026 GILD widened the web search and added six accounts. They include Level 12's VP of Engineering on the company blog, The New Stack's Auggie CLI beta review, and Robert Matsuoka's Hyperdev newsletter. The others are the ProjDevBench benchmark and two GitHub issues. Reddit, where much of the October 2025 pricing debate took place, is outside the record. An account counts when its author reports their own use of Augment's agent. GILD left out employee posts, vendor pages, affiliate reviews, and sponsored videos without a substantive account. Each account is tagged for the themes it clearly supports, with verbatim evidence kept in GILD's research workspace. A GitHub issue counts as mixed unless its author rejects or abandons Augment or recommends against it. Every finding rests on at least 5 accounts from 3 different authors, and every disagreement on at least 2 accounts per side.
Products in this piece
Sources
- Official documentation
- 6
- Public source
- 8
- Augment docs: Token-based pricing
- Augment Code pricing
- Augment docs: Completions
- Augment blog: Augment Code's pricing is changing on October 20, 2025 (Oct 6, 2025)
- Augment docs: Introducing Auggie CLI
- Augment blog: Augment Code's next chapter (Oct 8, 2026)
- LeadDev: How Tilt's review bot transformed its code reviews (Oct 8, 2025)
- LeadDev: How Collectors learnt to assess AI coding tools (Oct 15, 2025)
- Paul Schleger: Getting the most out of Augment Code at Cyoda (Sep 20, 2025)
- Hacker News: Augment confidently wrong with full source code (Dec 2, 2025)
- Hacker News: a team of four rewriting a legacy CRM with Auggie CLI (Mar 15, 2026)
- Hacker News: a team that moved from Augment Code to Claude Code (May 18, 2026)
- Hacker News: leaving Augment Code after its new pricing (Jan 8, 2026)
- AI Coding Daily: Augment Code vs Claude Code on three Laravel tests (Aug 18, 2025)