Cursor Memories

https://docs.cursor.com/context/memories

Project-scoped memories in Cursor, created either by a background 'sidecar' model watching chats or by the agent via tool calls, and managed as auto-generated rules in settings. Traction: First-party feature of one of the most widely used AI IDEs. As of 2026-10-29 the Memories docs page redirects to the Cursor docs home, which no longer documents Memories; Rules remain the documented persistent-context mechanism.

Active · Verified 2026-10-29 · fresh as of 2026-10-29 · 14 cited facts, 1 with a third-party source · 1 recorded change · Suggest a correction

At a glance

Type
Product vendor fix
Tier
T3
Created
searched not found fix
Latest release
searched not found fix
License
proprietary vendor fix
GitHub
not applicable — no GitHub repo fix
Pricing
searched not found fix
Funding
searched not found 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
Accelerator
ai-grant third-party fix
SDK languages
python, rest, typescript vendor fix
Protocols
mcp-client vendor fix

Memory taxonomy

storage
proprietary
retrieval
injection
persistence
cross-session
update
extraction
unit
fact
governance
editable
conflict
n/a

When to use

Optimised for: searched not found

Anti-fit: searched not found

Pros & cons

Pros

searched not found

Cons

searched not found

Claims & capabilities

Cursor is a coding agent for building ambitious software. Use it to understand your codebase, plan and build features, fix bugs, review changes, and work with the tools you already use.

Technical surface

API surface
searched not found
Backend storage
searched not found
Deployment
searched not found
Embedding model
searched not found
Multi-tenancy
searched not found
MCP
searched not found
A2A
searched not found
OpenTelemetry
searched not found

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 (13 cited facts, 1 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-23 Added to the catalog #222