Augment Code
Real-time knowledge graph indexed from connected repos + commit history + CI/CD + tickets + docs. Separate Agent Memory layer (Sept 2025) captures session decisions/corrections/goals as discrete items with developer review/approval UI. MCP endpoint exposes the graph.
At a glance
- Type
- Real-time semantic Context Engine + curated Agent Memory
- Tier
- T1
- Section
- Coding-agent memory
- Created
- 2023-01
- Latest release
- not applicable — not OSS
- License
- not applicable — not OSS
- GitHub
- not applicable — no GitHub repo
- Pricing
- Free + paid
- Funding
- $252M total $977M val Series B · 2024-04
Taxonomy
- storage
- graph
- retrieval
- graph-traversal
- persistence
- long-term
- update
- extraction
- unit
- document
- governance
- opaque
- conflict
- none
When to use
Optimised for: real-time semantic Context Engine across repos / commits / CI
Anti-fit: not for non-coding tasks
Pros & cons
Pros
Codebase-level semantic graph (Context Engine) gives precise navigation across very large repos that confuse generic file-context tools.
Cons
Heavyweight indexing makes initial setup slow on large codebases; pricing is enterprise-tier.
Claims & capabilities
$227M Series B (~$252M total); ~$977M valuation; 100k+ devs. Scales to 400k+ files.
Technical surface
- API surface
- not applicable — IDE plugin
- Backend storage
- custom
- Deployment
- Both
- Embedding model
- locked
- Multi-tenancy
- Proof-of-Possession API architecture: each request includes hardware-backed proof of codebase ownership; eliminates cross-tenant contamination by design
- MCP
- via official adapter — Augment MCP
- A2A
- searched not found
- OpenTelemetry
- searched not found
Compare Augment Code with…
Similar systems
Other coding-agent memory in the catalog, ranked by inbound references.
- Aider T2
Appends conversation turns to .aider.chat.history.md in project root. restore_chat_history defaults to false — no automatic replay into new sessions. Community /session save command for JSON state snapshots. .aider.conf.yml carries static preferences.
- Bolt.new (StackBlitz) T2
In-browser WebContainer (Rust-backed shared memory) is the implicit state store. No dedicated memory abstraction — project files are the state. Team plan adds shared workspaces + GitHub integration.
- Continue.dev Memory MCP T2
Official Memory MCP (Mar 2025) backed by a knowledge graph. Memory is injected via MCP rather than native to the Continue core. Scope depends on MCP server deployment (local or shared).
- Devin (Cognition) T1
Structured Knowledge items stored server-side. Three-tier scope: repo-pinned (always injected), global (recall by relevance), org/enterprise (visible to org members). Auto-generates Repo Knowledge from repo structure each session; reads past session trajectories for self-improvement; writes notes for recurring scheduled tasks.
- Lovable T2
Long-term context stored as files in /docs that the agent reads on each session. Agent Mode (default since July 2025) holds working context within session but doesn't persist cross-session beyond filesystem state.
- Mistral Vibe (Remote Agents) + Mistral Medium 3.5 T1
Vibe is Mistral's cloud-hosted coding-agent platform: each session runs in an isolated sandbox with task state, history, and approvals. Spawnable from CLI or Le Chat, with parallel execution. Local CLI sessions can be "teleported" to the cloud and resumed. Powered by Mistral Medium 3.5 (77.6% SWE-Bench Verified). Plugs into GitHub, Linear/Jira, Sentry, Slack/Teams.