Skip to main content

HarnessAI Coding Agent

Auggie CLI

Coding agent for the terminal and CI, built by Augment Code and owned by Harness since October 8, 2026, when Harness acquired Auggie CLI, Cosmos, and the Context Engine. It shares its agent and Context Engine with the Augment extensions for VS Code and JetBrains IDEs.

The 30-Second Take

Pick Auggie CLI if finding the right code in a large codebase is what slows your agents.

Its Context Engine, a semantic index, hands the model the code a task touches. The same agent runs in the terminal, CI and Augment's VS Code and JetBrains extensions.

Best fit
Teams on large or multi-repository codebases that want the same agent wherever engineers work.
Main constraint
Below Enterprise there is no budget cap, and Augment adds a 40% service fee to every model call.
First move
Point it at your largest repository with an .augmentignore, a rules file and a model policy.

Why

Watch the bill and the owner: usage bills at model list price plus a 40% fee, with budgets Enterprise-only. Harness acquired Auggie CLI in October 2026 along with the Context Engine, so review the contract for the move.

Practitioner sentiment, all practitioners+59 Strong positive

37 practitioners, 88 sources reviewed, Updated Nov 1, 2026How this is measured

Read the GILD Review
Save a product your organization uses.Keep up with Auggie CLI without adding it to your stack.Visit Website
Operating stack
Agentic Software Development

Comparisons

How does Auggie CLI compare with the alternatives?

  1. Auggie CLI vs Cursor

    • AI Coding Agents

    Pick Auggie CLI if engineers keep their own editors, and Cursor if the team will move into Cursor's editor. Both meter model usage past the plan, so compare context quality on your largest repository and how each caps team spend.

  2. Pick Auggie CLI for models from several providers and context from Augment's semantic index. Pick Claude Code for Anthropic models under Claude plans and an agent that searches the repository itself. Count accepted changes and cost on the same repository before you commit.

Operator Insights

What are engineering leaders learning from deploying Auggie CLI?

Buying and deployment

What engineering leaders should verify before a broader rollout.

Sourced from Augment Code documentation

How you buy it

US$20

A month for Standard, a flat price for up to 50 seats. Business is US$100.

Source 1, Augment Code, Pricing: PricingSource 2, Augment Code, Token-based pricing: Token-based pricing

Details

Standard costs US$20 per month or Business US$100 per month, each a flat price for up to 50 seats with the same dollar amount of pooled monthly usage. Enterprise is custom, with unlimited users.

Cost drivers

40% fee

On LLM spend at list price, plus Cosmos compute at US$0.19 an hour.

Source 2, Augment Code, Token-based pricing: Token-based pricing

Details

Usage is billed in dollars: model tokens at the provider's public API list price, a 40% service fee on that LLM spend, and Cosmos compute at US$0.19 per hour. Usage past the plan continues pay as you go.

Where it runs

CLI, IDE, cloud

The CLI on Node 20 or later, VS Code and JetBrains extensions, CI, and Cosmos agents.

Source 3, Augment Code, Introducing Auggie CLI: Introducing Auggie CLI

Details

Auggie CLI, installed from npm anywhere Node 20 or later runs. Other options are ACP clients, Vim and Neovim, the Augment VS Code and JetBrains extensions, CI pipelines, and Cosmos cloud agents.

What to verify

Code upload

Indexing uploads your code, and the IDE extension does not enforce tool permission rules.

Source 3, Augment Code, Introducing Auggie CLI: Introducing Auggie CLISource 4, Augment Code, Tool permissions: Tool permissionsSource 1, Augment Code, Pricing: Pricing

Details

Check that automatic indexing of your project by Augment's context engine is acceptable. Confirm that tool permission rules cover your policy (the CLI and Cosmos enforce them, the IDE extension does not). Establish what Harness ownership changes in your contract.

Signals

What is the current evidence saying about Auggie CLI?

A current read of what engineering leaders, teams, and individual builders report publicly about Augment Code's agent, in Auggie CLI and the Augment IDE extensions, with every finding linked to its sources.

Whose sources count

Practitioner sentiment, all practitioners

+59 Strong positive net

of 42 sources that take a side, each author counted once.

How this figure is made

18 more state no overall view and cast no vote.

Leaders and teams have 8 accounts; GILD prints their sentiment from 20.

Current sentiment

Positive, mixed and negative sources

The score counts them as 23 positive, 13 mixed and 1 negative votes, one per author.

The read is positive, led by praise for how the Context Engine finds the right code: 21 of the 22 sources that discuss it are positive. Speed and reliability is the most frequent concern, raised by all 9 sources that discuss it, and practitioners split evenly, 6 to 6, on staying with Augment or moving.

Use a task pilot to measure accepted work and review time.

Evidence field. All 88 sources, one mark each.

Arrange by

Each mark is one source: positive, mixed, negative, no opinion stated, or documentation (not counted).

By sentiment, All practitioners. Every source GILD read, grouped as the field draws it.
GroupSourcesPositiveMixedNegativeNo opinion stated and not counted in the scoreDocumentation, checked and not counted
Positive26260000
Mixed15015000
Negative100100
Not counted25000250
Documentation21000021
Every source GILD read, by the quarter it was published, as the field's time axis counts it. Documentation is dated by the day it was checked.
QuarterSources
Q1 20252
Q2 202519
Q3 202516
Q4 202512
Q1 202610
Q2 20267
Q3 20261
Documentation, checked21

By sentiment

21 documentation pages check facts and are not counted.

Hover a mark for a quick look, click it or press Enter to open its source.Tap a mark to open its source, then step to its neighbors with Previous and Next.

What practitioners praise

Top praise of 4. Each mark is a source on it; filled marks praise it.

  1. Context Engine21 of 22 sources on it praise it

Most common concerns

Top concern of 4. Each mark is a source on it; filled marks raise it.

  1. Speed & ReliabilityAll 9 sources on it raise it as a concern
All 88 sources behind these findings
  1. PricingAugment Code (Official), Product documentation, checked Oct 12, 2026
  2. Token-Based PricingAugment Code (Official), Product documentation, checked Oct 12, 2026
  3. Available ModelsAugment Code (Official), Product documentation, checked Oct 12, 2026
  4. Introducing Auggie CLIAugment Code (Official), Product documentation, checked Oct 12, 2026
  5. Install Auggie CLIAugment Code (Official), Product documentation, checked Oct 12, 2026
  6. Index your workspace (CLI)Augment Code (Official), Product documentation, checked Oct 12, 2026
  7. Index your workspace (VS Code)Augment Code (Official), Product documentation, checked Oct 12, 2026
  8. Tool PermissionsAugment Code (Official), Product documentation, checked Oct 12, 2026
  9. Rules & GuidelinesAugment Code (Official), Product documentation, checked Oct 12, 2026
  10. Using Auggie with AutomationAugment Code (Official), Product documentation, checked Oct 12, 2026
  11. Service AccountsAugment Code (Official), Product documentation, checked Oct 12, 2026
  12. ACP ClientsAugment Code (Official), Product documentation, checked Oct 12, 2026
  13. Install Augment for Visual Studio CodeAugment Code (Official), Product documentation, checked Oct 12, 2026
  14. Install Augment for JetBrains IDEsAugment Code (Official), Product documentation, checked Oct 12, 2026
  15. CompletionsAugment Code (Official), Product documentation, checked Oct 12, 2026
  16. Context Engine MCPAugment Code (Official), Product documentation, checked Oct 12, 2026
  17. Usage Dashboards & BudgetsAugment Code (Official), Product documentation, checked Oct 12, 2026
  18. Setup Guide for Business Plan (Code Review)Augment Code (Official), Product documentation, checked Oct 12, 2026
  19. Getting Started with CosmosAugment Code (Official), Product documentation, checked Oct 12, 2026
  20. Security & PrivacyAugment Code (Official), Product documentation, checked Oct 12, 2026
  21. Augment Code's next chapterAugment Code (Official), Product documentation, checked Oct 12, 2026
  22. Comment on: ACP mode: host-supplied mcpServers in session/new replace (rather than merge with) settings.json/.mcp.json serversJulian Mesa, integrating Auggie into GitKraken Kepler (self-described: GitKraken Kepler, which drives Auggie 0.36.0 over ACP), GitHub issue comment, published Sep 17, 2026
  23. Multi-minute event-loop freeze in uv__fsevents_close (macOS) when indexing/file-watching is enabledinercia, Auggie CLI user running it under an ACP host (self-described: Large workspaces on macOS, Auggie 0.28.0 in ACP mode with indexing on), GitHub issue, published Jun 4, 2026
  24. [Bug]: Denying launch-process doesn't block file deletion - agent silently falls back to remove-filesharjothkhara, Auggie CLI user testing tool permissions (self-described: Auggie 0.28.0 in print mode with toolPermissions), GitHub issue, published Jun 3, 2026
  25. Comment on: Show HN: Semble - Code search for agents that uses 98% fewer tokens than grepparasti, developer whose team moved off Augment (self-described: Team at work, moved from Augment Code to Claude Code), Hacker News comment, published May 18, 2026
  26. Comment on: Task Paralysis and AIrsyring, Hacker News commenter (self-described: Augment agents in VS Code and the CLI for about eight months), Hacker News comment, published May 10, 2026
  27. Comment on: Ask HN: What do you still do manually in 2026 that should be automated?RanHal, Hacker News commenter (self-described: Personal knowledge base), Hacker News comment, published May 7, 2026
  28. [Feature]: Project-scoped hooks (.augment/settings.json checked into the repo)kwalitynut, member of a Clari developer-experience team (self-described: Team building an AI-provenance commit standard for Augment and Claude Code users), GitHub issue, published May 1, 2026
  29. Comment on: Show HN: MTTCleaner - Same as CCleaner but free, no adsmytechtoday, IT consultant (self-described: Solo IT consultant building PowerShell tools for clients), Hacker News comment, published Apr 26, 2026
  30. Comment on: Ask HN: How is AI-assisted coding going for you professionally?parasti, developer on a team of four rewriting a legacy CRM (self-described: Team of 4, full rewrite of a 30-year-old CRM in Laravel), Hacker News comment, published Mar 15, 2026
  31. Comment on: OpenAI raises US$110B on US$730B pre-money valuationhn_acc1, developer whose company standardizes on Augment (self-described: C++ work in VS Code), Hacker News comment, published Feb 27, 2026
  32. Predatory credit pricing: --print re-indexes workspace on every call, burning 2000+ credits per queryfodurrr, GitHub user (self-described: Solo, scripting Auggie CLI in print mode on the Indie plan), GitHub issue on augmentcode/auggie, published Feb 20, 2026
  33. AI DevOps: Building Intelligent Incident Response SystemsKyle Getty, software engineer at Tilt (Tilt on-call engineering on Azure, alert-triggered incident analysis), Company engineering blog post, Tilt, published Feb 13, 2026
  34. ProjDevBench: Benchmarking AI Coding Agents on End-to-End Project DevelopmentPengrui Lu and five co-authors, academic researchers (self-described: Independent benchmark of six coding agents through their command-line interfaces on 20 project-building tasks), Independent benchmark, research paper on arXiv, published Feb 2, 2026
  35. [Bug]: 0.15.0 Context exceedsyann0001, Auggie CLI user, self-described, GitHub issue, published Jan 30, 2026
  36. Sub-agents bypass CLI permission enforcement (security gap) - v0.14.0JonatanRoo, GitHub user (self-described: Solo, using Auggie for all development for several months), GitHub issue on augmentcode/auggie, published Jan 30, 2026
  37. Comment on: Ask HN: Do you have any evidence that agentic coding works?defatigable, Hacker News commenter (self-described: Golang and Python at work), Hacker News comment, published Jan 21, 2026
  38. Comment on: Ask HN: Do you have any evidence that agentic coding works?fmdv, Hacker News commenter (self-described: PowerShell development), Hacker News comment, published Jan 21, 2026
  39. Comment on: How Google got its groove back and edged ahead of OpenAImythz, Hacker News commenter (self-described: Full-time coding assistant user), Hacker News comment, published Jan 8, 2026
  40. Comment on: Claude Code gets native LSP supportatombender, Hacker News commenter (self-described: Uses Augment completions with Claude Code for agent work), Hacker News comment, published Dec 23, 2025
  41. Comment on: Claude Code gets native LSP supportvb-8448, Hacker News commenter (self-described: Uses PyCharm), Hacker News comment, published Dec 22, 2025
  42. Comment on: Ask HN: How can I get better at using AI for programming?adam_patarino, founder of Cortex.build (self-described: Builds a competing context product), Hacker News comment, published Dec 18, 2025
  43. Comment on: Launch HN: Nia (YC S25) - Give better context to coding agentskenforthewin, Hacker News commenter, self-described, Hacker News comment, published Dec 8, 2025
  44. Comment on: OpenAI declares 'code red' as Google catches up in AI racedanielodievich, engineer working with the company's support team (self-described: Company support and engineering, answering a customer question), Hacker News comment, published Dec 2, 2025
  45. Comment on: Developers are choosing older AI modelsfeintruled, Hacker News commenter, self-described, Hacker News comment, published Nov 5, 2025
  46. Comment on: </> Htmx - The Fetch()eningnchmy, Hacker News commenter, self-described, Hacker News comment, published Nov 3, 2025
  47. [Bug]: New version of Auggie (v0.6.0) having delayed responsesrishitank, Auggie CLI user (self-described: macOS, zsh), GitHub issue, published Oct 31, 2025
  48. Roo Code vs. Copilot vs. Cline vs. Kilo Code vs. Augment Code: The Ultimate Coding Assistant.Codewello, developer and YouTube creator (self-described: Compares five VS Code assistants the channel uses), Video, YouTube, published Oct 27, 2025
  49. How Collectors learnt to assess AI coding toolsDan Van Tran, CTO of Collectors, with staff engineer Alex (self-described: Collectors (PSA, PCGS), about 220 engineers, structured trials of several AI tools), Webinar in a LeadDev series produced with Augment Code, LeadDev (YouTube), published Oct 15, 2025
  50. Comment on: Vibe engineeringkeithnz, Hacker News commenter (self-described: Front-end work), Hacker News comment, published Oct 8, 2025
  51. How Tilt's review bot transformed its code reviews, with Augment CodeJames Garrett, staff engineer at Tilt (self-described: Tilt backend engineering, monolithic codebase, teams across US and Australian time zones), Webinar in a LeadDev series produced with Augment Code, LeadDev (YouTube), published Oct 8, 2025
  52. Getting the Most out of Augment CodePaul Schleger, Cyoda (self-described: Cyoda engineering team, six months of daily use, mostly IntelliJ IDEA with Java and Kotlin), Engineering team write-up, Substack (Paul Schleger), published Sep 20, 2025
  53. Beyond the Purchase Order: How We Actually Made AI Work for EngineeringJames Garrett, backend developer at Tilt (Tilt fintech engineering, rules shared across the team), Company engineering blog post, Tilt, published Sep 11, 2025
  54. Augment Code's Auggie: When Focused Single-Process Beats Multi-AgentRobert Matsuoka, fractional CTO and former CTO of Tripadvisor (self-described: Solo, debugging his open-source Claude MPM framework, a long-time Claude Code user), Newsletter post, Hyperdev (Substack), published Sep 4, 2025
  55. Comment on: Claude Code: Now in Beta in Zedatombender, Hacker News commenter (self-described: Uses Augment in JetBrains IDEs; colleagues use Cursor), Hacker News comment, published Sep 3, 2025
  56. How Webflow Got 89% of Its Engineers To Use AI DailyAllan Leinwand, Chief Technology Officer at Webflow (Webflow engineering, about 300 engineers with Cursor and Augment Code in a company AI toolkit), Interview article, The New Stack, published Aug 29, 2025
  57. Auggie CLI + Sonnet 4: The BEST Agentic Terminal I've Tried Yet (Augment Code CLI)Nathan Sebhastian, developer and YouTube creator (self-described: Builds a CRM dashboard in Auggie CLI), Video, YouTube, published Aug 29, 2025
  58. Developer Walk-Through of Auggie CLI, an Agentic Terminal AppDavid Eastman, London-based software developer and consultant, writing for The New Stack (self-described: Solo, trying the private beta on his own Ruby on Rails tool for a game), Independent review article, The New Stack, published Aug 23, 2025
  59. Augment Code: Worth US$50/Month? Three Tests vs Claude CodePovilas Korop, Laravel developer and creator of AI Coding Daily (self-described: Laravel project, three tasks run side by side in Augment and Claude Code), Video, YouTube, published Aug 18, 2025
  60. Comment on: Vibe coding is the fast fashion industry of software engineeringlemiffe, Hacker News commenter (self-described: dbt, PHP and TypeScript codebases), Hacker News comment, published Aug 1, 2025
  61. Augment Code releases CLI Claude Code competitor Auggie (reply)Ricky Guo, daily Augment user (self-described: Moved from Cursor and Windsurf in spring 2025; uses VS Code), Product Hunt forum reply, published Jul 31, 2025
  62. Building with AI: How Webflow engineers move faster, think deeper, and ship smarterAllan Leinwand, Chief Technology Officer at Webflow (Webflow engineering, where every engineer gets Augment Code beside Cursor), Company engineering blog post, Webflow Blog, published Jul 16, 2025
  63. Comment on: Ask HN: What are your favorite coding tools?physix, Hacker News commenter (self-described: Uses the plugin in IDEA and PyCharm), Hacker News comment, published Jul 15, 2025
  64. Comment on: Ask HN: Where are the AI-driven profits or promotions?gavinray, engineer at a company that rolled out Copilot and Augment (self-described: Company provides Copilot and Augment), Hacker News comment, published Jul 13, 2025
  65. Comment on: OpenAI's Windsurf deal is off, and Windsurf's CEO is going to Googlee1g, Hacker News commenter (self-described: 6 to 10 hours a day across mid-size codebases), Hacker News comment, published Jul 12, 2025
  66. Comment on: OpenAI's Windsurf deal is off, and Windsurf's CEO is going to Googlelp4x, Hacker News commenter, self-described, Hacker News comment, published Jul 12, 2025
  67. Comment on: Show HN: I AI-coded a tower defense game and documented the whole processM4v3R, developer using Augment at a day job and on a side project (self-described: Medium-sized codebase at a day job), Hacker News comment, published Jul 4, 2025
  68. Comment on: Ask HN: What useful AI tools do you use every day?chime, Hacker News commenter (self-described: Has tried most AI editors and CLI agents), Hacker News comment, published Jun 25, 2025
  69. Comment on: Agentic Coding Recommendationschuckadams, Hacker News commenter (self-described: Works in JetBrains IDEs), Hacker News comment, published Jun 12, 2025
  70. Comment on: Cursor 1.0gondo, Hacker News commenter (self-described: Works in GoLand, Android Studio and other JetBrains IDEs), Hacker News comment, published Jun 5, 2025
  71. Comment on: Claude Code is now available to Pro plansmythz, Hacker News commenter (self-described: Uses VS Code and Rider), Hacker News comment, published Jun 4, 2025
  72. Comment on: Human coders are still better than LLMshn_acc1, developer whose company allows only Augment (self-described: Company standard: the only AI tool allowed), Hacker News comment, published May 30, 2025
  73. Comment on: Why Cline doesn't index your codebasenchmy, Hacker News commenter, self-described, Hacker News comment, published May 28, 2025
  74. Comment on: Why Cline doesn't index your codebasechime, Hacker News commenter (self-described: Large monorepo), Hacker News comment, published May 27, 2025
  75. Comment on: Why Cline doesn't index your codebasejjani, Hacker News commenter, self-described, Hacker News comment, published May 27, 2025
  76. Comment on: The unreasonable effectiveness of an LLM agent loop with tool usecheema33, Hacker News commenter (self-described: Works in a git repo with several LLMs reviewing each other), Hacker News comment, published May 20, 2025
  77. My Augmented Coding Tools As Of 16 May 2025Kent Beck, software developer and author (self-described: Personal projects in VS Code and IntelliJ), Newsletter, Software Design: Tidy First? (Substack), published May 16, 2025
  78. Comment on: Perverse incentives of vibe codingphysix, Hacker News commenter (self-described: Uses the plugin in IntelliJ and PyCharm), Hacker News comment, published May 15, 2025
  79. Comment on: My 600 Hours with AI Coding Assistants: A Practical Comparisonbv_dev, Hacker News commenter (self-described: Over 600 hours across AI coding assistants in three months), Hacker News comment, published May 14, 2025
  80. Comment on: Cline is quietly eating Cursor's lunch and changing how we codereplwoacause, Hacker News commenter (self-described: Pays for several assistants at once), Hacker News comment, published May 8, 2025
  81. Comment on: OpenAI reaches agreement to buy Windsurf for US$3Bsagarpatil, Hacker News commenter (self-described: Windsurf customer since launch), Hacker News comment, published May 7, 2025
  82. Comment on: Cursor hits US$9B valuationevelant, Hacker News commenter, self-described, Hacker News comment, published May 5, 2025
  83. Building UI with AIMatt Lewellyn, VP of Engineering at Level 12 (Level 12, a Louisville software consultancy, on a client project with a Bootstrap template), Company blog post, Level 12, published Apr 30, 2025
  84. Comment on: The Future of MCPsbluedevil2k, engineer building internal tooling for the company's frontend developers (self-described: Company with an API layer of over 1,000 endpoints), Hacker News comment, published Apr 23, 2025
  85. Augmented Coding: an Experience ReportJessica Kerr (Jessitron), software developer (self-described: Weekend project: an app implemented in three to four languages), Personal blog post, jessitron.com, published Apr 20, 2025
  86. AI Agent-Driven Development with Augment CodeMatt Lewellyn, VP of Engineering at Level 12 (Level 12, a Louisville software consultancy building Python SaaS apps for clients), Company engineering blog post, Level 12, published Apr 11, 2025
  87. FREE Augment Code Beats Cursor & Windsurf For Large Codebase Indexing!Josh Pocock, founder of Executive Stride and YouTube creator (self-described: His company's Next.js site), Video, YouTube, published Feb 22, 2025
  88. Comment on: GitHub Copilot: The Agent Awakensilrwbwrkhv, Hacker News commenter, self-described, Hacker News comment, published Feb 6, 2025

Feb 2025 to Sep 2026.

67 sources from practitioners, by month and sentiment.

The full readExplore all Auggie CLI Signals4 praise themes, 5 concerns, 3 points of agreement and 2 disagreements across all three groups, with all 88 sources open to inspect.

Where It Fits

Where does Auggie CLI belong in the stack?

Auggie CLI is Core across Build, supports Plan and Validate, and touches Ship and Operate.

Business area
Product & Engineering
Function
Software Development
Operating stack
Agentic Software Development
Primary role
Codebase-Aware Coding Agent & CLI
Auggie CLI beside the rest of its stackThe Stack Field, every product on every layer
FootprintAuggie CLI across the Agentic Software Development stack. Bar height is its role on each layer.
  1. Plan

    1. Work planning: Supports

      Work planning, supports. The Task Manager breaks complex work into tracked steps inside a session; planning stays in the team's tracker.

  2. Build

    1. Codebase context: Core

      Codebase context, core. The Context Engine semantically indexes the workspace and related repositories, and other agents can query it over MCP; this is Augment's central capability.

    2. Coding: Core

      Coding, core. Auggie writes and changes code across a repository from the terminal, an ACP editor, or the Augment IDE extensions.

    3. Agent runtime: Core

      Agent runtime, core. The Auggie terminal interface, and the same agent in VS Code, JetBrains IDEs, Zed, Neovim, and Emacs, is where engineers steer and review its work.

    4. Tool execution: Supports

      Tool execution, supports. Auggie runs terminal commands and MCP tools under allow, deny, webhook, or script permission rules, but tool orchestration is not its center.

  3. Validate

    1. Debugging: Supports

      Debugging, supports. Auggie investigates failures with repository context, and print mode can summarize build logs piped into it.

    2. Testing: Supports

      Testing, supports. Auggie can write and run tests as part of a task, but it does not replace dedicated testing infrastructure.

    3. Code review: Supports

      Code review, supports. Augment Code Review and the review-pr GitHub Action comment on pull requests with codebase context; merge decisions stay with the engineering team.

    4. Application security: Touches

      Application security, touches. Reviews and custom commands can flag security issues, but Augment is not a dedicated application-security platform.

  4. Ship

    1. Source control: Touches

      Source control, touches. Auggie connects to GitHub for reviews, actions, and indexing, and can commit and push; Git stays the system of record.

    2. CI/CD: Touches

      CI/CD, touches. Auggie runs headless in GitHub Actions, Jenkins, and other pipelines with service accounts; delivery stays in the team's CI/CD.

  5. Operate

    1. Observability: Touches

      Observability, touches. Auggie can triage alerts and exceptions in automation, but it does not provide observability itself.

Market mapThe layers Auggie CLI covers, and who else owns each one.

  1. Codebase context & intelligence

    CoreBuild

  2. Coding & implementation

    CoreBuild

  3. Agent interface & developer runtime

    CoreBuild

  4. Work planning & task decomposition

    SupportsPlan

  5. Tool execution & integrations

    SupportsBuild

7 more layers on the full map. Core, Supports and Touches describe coverage. They say nothing about quality.

More on Auggie CLI

  1. GILD ReviewGILD's evaluation, with the buying facts
  2. Research2 pieces
  3. Guides4 guides
  4. Operator Insights3 operator accounts
  5. Where It FitsOn the Agentic Software Development stack
  6. Related Products8 products