Continue the conversation — chat opens pre-seeded with the current signal, caps, and movement.
Enterprise AI coding platform built around a best-in-class Context Engine that indexes 500K+ files with cross-repo dependency graph awareness at ~100ms retrieval. Target user: enterprise engineering organizations with large codebases where context fidelity (not raw model speed) is the binding constraint. Strongest fit for F500 teams that have already evaluated Cursor or Claude Code and hit context-window walls on their monorepo.
Differentiator: #1 SWE-bench Pro ranking (51.80%); Context Engine retrieval depth; Cosmos agentic OS adding team-wide shared memory and event bus (MAX-only preview as of May 2026); Intent multi-agent workspace orchestrating up to 6 specialist agents in parallel git worktrees (public beta, macOS-only). Prism model router delivers 20–30% cost reduction vs frontier models. ISO/IEC 42001 plus SOC 2 Type II.
Product pivot (March 31 2026): Augment removed inline completions (Next Edit + Completions) and retired the Indie, Standard, and Legacy plans, fully pivoting to the Intent agentic workflow model. Teams expecting traditional inline autocomplete must adapt to the Intent paradigm.
Adoption & Proof Points
- Publicly named F500 and enterprise customers:
- **DXC Technology** — Fortune 500, 50,000-developer organization; case study reports an environmental-health-and-safety product scoped at one year reaching beta-quality in 10 days, and a GIS feature (normally a sprint or two) shipped in hours
- **Tekion** — 1,300+ engineers, 50–100% productivity gains, 90%+ test coverage with persona-driven agents
- **Pure Storage** — 2,000 engineers, 3x velocity target
- **MongoDB, WEX, Intercom, Rubrik, LendingTree** and others publicly referenced
- Business signals: $252M total funding, $977M post-money valuation, ~172–188 employees, ~$20M ARR (Latka), weekly release cadence. #1 SWE-bench Pro (51.80%, Scale AI) is independently published. Adoption evidence is strong but remains vendor-published logos plus one independent benchmark — short of the documented hands-on/third-party trial bar for Assessed.
Recommended Use Cases
- **Monorepo-scale enterprises blocked by context limits** — organizations where Cursor or Claude Code have already failed on large codebases; Context Engine's 500K-file, cross-repo, ~100ms retrieval is the direct solution to that binding constraint.
- **F500 teams with strict data-sovereignty requirements** — air-gapped, VPC, or on-prem deployment plus CMEK, zero data retention, single-tenant instances, and ISO/IEC 42001 + SOC 2 Type II make Augment the strongest compliance posture in the agentic IDE category short of FedRAMP.
- **Engineering orgs ready to commit to agentic-first workflows** — following the March 31 2026 removal of inline completions, Augment is appropriate only for teams willing to operate within the Intent Coordinator→Specialists→Verifier model; teams dependent on suggestion-based autocomplete should evaluate alternatives.
- **Large-scale parallel feature development on macOS** — Intent's multi-agent git worktree orchestration is suited to teams that can absorb the macOS-only constraint and want to run up to six specialist agents concurrently across independent branches.
- **Enterprises requiring auditable AI governance** — SAML SSO/OIDC/SCIM, granular RBAC, SIEM-integrated audit logs, and sandboxed agent execution satisfy procurement requirements in regulated industries; GDPR, CCPA, and HIPAA compliance now claimed.
- **Organizations with heterogeneous toolchains** — native agent integrations across GitHub, Linear, Jira, Confluence, Notion, Sentry, and Stripe, plus Enterprise Slack and VS Code/JetBrains/Vim/Neovim parity, reduce integration friction for teams that cannot standardize on a single vendor stack.
Risks & Limitations
- **Product pivot — inline completions removed (March 31 2026):** Augment discontinued its Next Edit and Completions features on March 31 2026, retiring the Indie, Standard, and Legacy plans and pivoting fully to the Intent multi-agent workflow model. Teams that relied on Augment for traditional inline autocomplete must migrate to Intent or seek an alternative. This represents a significant workflow change that may affect adoption in teams accustomed to suggestion-based tooling.
- **Pricing controversy:** credit-based model with quantified burn (e.g., community reports of ~51K credits/day; a complex Sonnet 4.5 task ~4,261 credits ≈ 3.3% of a Standard monthly budget); sustained r/AugmentCodeAI 'bait-and-switch' sentiment over the Oct 2025 credit migration; polarized reviews (G2 2.8/5 from 2, vs Gartner Peer Insights 4.8/5 from 40). Binding constraint on enterprise trust — but no NEW overhaul since the prior eval, so no `pricing-volatility` cap applied
- **Leadership transition:** CEO changed from Scott Dietzen to Matt McClernan (joined Dec 2025) in early 2026 — planned succession with founders intact, logged as a viability watch item
- **Platform fragmentation:** Intent is macOS-only (public beta; Windows on waitlist with no timeline); Cosmos is MAX-tier-only preview
- **Reliability complaints:** documented crashes, HTTP 400/502 errors, endless loops, occasional invented APIs in community reports — same complaints as the prior eval with no new escalation; not cap-triggering against benchmark-leading capability
- **Revenue maturity:** ~$20M ARR is below mature Market-Leader band; viability score 16 reflects strong adoption against limited revenue scale
- **No hands-on validation by our team:** evaluation depth is `thorough` (research-based, multi-source, Opus 4.8 re-baseline) but `handsOn = not_tested`; advancement to Assessed requires direct trial or independent third-party evaluation
Capabilities & Integration
**Agentic capability (autonomy 16, bottom of Self-Directed band):** Cosmos agentic OS in MAX preview (Expert Registry, shared memory, coordinated SDLC agents); Intent (macOS beta) with a Coordinator→parallel Specialists (git worktrees)→Verifier loop and spec-driven autonomous multi-repo execution; Remote Agents for background/async execution. #1 SWE-bench Pro at 51.80% (Scale AI).
**Context (17, Ecosystem-Aware):** Context Engine indexes up to 500K files at ~100ms retrieval, cross-repo with a live semantic index of code, dependencies, architecture, commit history, docs, and wikis — the primary category differentiator validated by the DXC outcome.
**Integration (14, IDE-Native/Team-Aware):** Native Augment Agent integrations for GitHub, Linear, Jira, Confluence, Notion, Sentry, Stripe; Enterprise Slack; in-editor PR workflows; Auggie CLI; GitHub Actions; Context Engine MCP. Remaining gap: Microsoft Teams and deep CI/CD-native review orchestration.
**Interface (15, Multi-Platform strong):** VS Code, all JetBrains IDEs (2024.3+), Vim/Neovim (feature parity), Auggie CLI with headless --no-tui mode, GitHub Actions, Intent (macOS), Cosmos web (MAX-only). Prism model router (Claude+Gemini / GPT+Kimi) for cost-optimized model selection.
