Catalog Systems Coding-agent memory Continue.dev Memory MCP

Continue.dev Memory MCP

https://hub.continue.dev/continuedev/memory-mcp

Discontinued: Continue was bought by Cursor (announced ~2026-06-16); the product is discontinued and the continuedev/continue repo is read-only. 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).

Archived. repository archived (read-only) Source · Alternatives and migration notes →

Archived · Verified 2026-10-29 · fresh as of 2026-10-29 · 37 cited facts, 6 with a third-party source · 3 recorded changes · Suggest a correction

At a glance

Type
KG-backed memory via MCP vendor fix
Tier
T2
Section
Coding-agent memory
Created
2023-06 (Continue.dev founded); Memory MCP March 2025 third-party fix
Latest release
not applicable — not OSS fix
License
not applicable — not OSS fix
GitHub
not applicable — no GitHub repo fix
Pricing
Discontinued — Continue acquired by Cursor; recurring billing disabled and unused paid credits refunded; Continue Hub (hub.continue.dev) offline vendor fix
Funding
$5.6M total raised: $2.1M (YCS23) + $3M SAFE led by Heavybit; acquired by Cursor (2026-06, terms undisclosed) third-party fix
Freshness
2026-10-29 fix
Layer
agent-infra repo fix
Licensing
commercial vendor fix
Accelerator
yc-s23 third-party fix

Memory taxonomy

storage
graph
retrieval
graph-traversal
persistence
long-term
update
extraction
unit
fact
governance
inspectable
conflict
none

When to use

Optimised for: KG-backed memory across IDE sessions

Anti-fit: not for non-coding tasks

Pros & cons

Pros

Open-source IDE extension with MCP-based memory — choose your own memory backend.

Cons

Memory quality bounded by chosen MCP server; setup more involved than first-party offerings.

Claims & capabilities

Hub package continuedev/rules-memory ; community integrations add worktree-aware queries.

Technical surface

API surface
searched not found
Backend storage
searched not found
Deployment
Both (VS Code/JetBrains extension local + optional shared MCP server)
Embedding model
searched not found
Multi-tenancy
searched not found
MCP
native (first-party)
A2A
not supported
OpenTelemetry
OpenTelemetry via Continue Enterprise; OSS edition has local logs only

Alternatives to Continue.dev Memory MCP → 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.

  • Augment Code T1

    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.

  • 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

Sources (36 cited facts, 6 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
    • Pricing “Free (OSS core); paid Continue Hub plans for teams (pricing on website)” → “Discontinued — Continue acquired by Cursor; recurring billing disabled and unused paid credits refunded; Continue Hub (hub.continue.dev) offline” source
    #309
  2. 2026-10-23
    • Funding / ownership “$5.6M total raised: $2.1M (YCS23) + $3M SAFE led by Heavybit” → “$5.6M total raised: $2.1M (YCS23) + $3M SAFE led by Heavybit; acquired by Cursor (2026-06, terms undisclosed)” source
    #223
  3. 2026-10-22
    • Lifecycle first recorded as “archived”
    #195

Related systems

References (2)