Catalog Systems Coding-agent memory Augment Code

Augment Code

https://www.augmentcode.com

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. Acquired by Harness (2026-10-08): Harness bought select Augment Code assets, including Cosmos, the Auggie CLI and the Context Engine, and the team joined Harness. augmentcode.com now leads with Cosmos, a software-factory agent platform.

Acquired. acquired by Harness Source · Alternatives and migration notes →

Acquired · Verified 2026-10-29 · fresh as of 2026-10-29 · 59 cited facts, 5 with a third-party source · 2 recorded changes · Suggest a correction

At a glance

Type
Real-time semantic Context Engine + curated Agent Memory vendor fix
Tier
T1
Section
Coding-agent memory
Created
2023-01 vendor fix
Latest release
not applicable — not OSS fix
License
not applicable — not OSS fix
GitHub
not applicable — no GitHub repo fix
Pricing
Standard $20/mo (incl. $20 usage, up to 50 seats); Business $100/mo (incl. $100 usage); Enterprise custom vendor fix
Funding
Acquired by Harness (2026-10-08; select assets incl. Cosmos, Auggie CLI, Context Engine); previously $252M total $977M val Series B · 2024-04 third-party fix
Freshness
2026-10-29 fix
Layer
agent-infra repo fix
Licensing
commercial vendor fix
Deployment locus
ide vendor fix
Platform vs product
product vendor fix
SDK languages
python, typescript vendor fix
Protocols
mcp-client, mcp-server vendor fix
Compliance
ccpa, gdpr, hipaa, iso42001, soc2-type2 vendor fix

Memory 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
yes — Augment Agent is an MCP client (Easy MCP, settings panel, JSON import)
A2A
searched not found
OpenTelemetry
searched not found

Compare Augment Code with…

Alternatives to Augment Code → live options ranked by shared design, licence, hosting and MCP support

Similar systems

Other coding-agent memory in the catalog, ranked by inbound references.

  • 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.

  • 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.

  • Letta Code T3

    Letta's stateful coding-agent harness: agents rewrite their own memory blocks and skills, version context in git via MemFS (syncable to GitHub) and reflect via a periodic /sleeptime 'dreaming' process. from Letta (MemGPT) team. letta-ai/letta-code is now the main Letta source (harness, terminal UI, App Server, channels); the Letta V1 API server was retired to the archive branch of letta-ai/letta.

  • Replit Agent T1

    No documented built-in persistent semantic memory store. Session duration expanded to 200 min (Agent 3); Agent 4 shifts toward persistent runtimes. Temporal used for orchestration durability, not semantic memory. Cross-session memory relies on filesystem + agent-written notes.

  • agentmemory (rohitg00) T3

    Self-hosted persistent memory layer that captures coding-agent activity and recalls it in later sessions, positioned on public benchmark results. #7 in TeleAI Awesome-Agent-Memory

  • Beads (Steve Yegge) T3

    Dolt-backed, dependency-aware graph issue tracker that acts as persistent structured memory for coding agents, replacing markdown plans; `bd remember` stores durable facts and `bd prime` re-injects them.

Sources (58 cited facts, 5 third-party)

Each fact links to the page it came from; the badge says who published it (how to read sources).

What changed

Changes to this record's lifecycle, licence, release, pricing and hosting facts, from the catalog's git history. Subscribe (Atom)

  1. 2026-10-29
    • Funding / ownership “$252M total $977M val Series B · 2024-04” → “Acquired by Harness (2026-10-08; select assets incl. Cosmos, Auggie CLI, Context Engine); previously $252M total $977M val Series B · 2024-04” source
    #305
  2. 2026-10-22
    • Pricing “Free + paid” → “Standard $20/mo (incl. $20 usage, up to 50 seats); Business $100/mo (incl. $100 usage); Enterprise custom” source
    • MCP support “via official adapter — Augment MCP” → “yes — Augment Agent is an MCP client (Easy MCP, settings panel, JSON import)” source
    #219

Related systems

Referenced by (1)

  • Langfuse integrates with — Langfuse's integrations directory has a Augment Code integration page. (verified 2026-10-29)