Cursor rules are not memory
A .cursor/rules file is static instruction. It does not remember which approach failed, which API decision was made, or which task is still blocked.
Memory for Cursor
Persistent memory for Cursor, without the cloud.
Awareness is a local-first memory layer for Cursor. It writes workflow rules into .cursor/rules, recalls structured knowledge through MCP, and keeps the data as Markdown on your machine. One setup works across Cursor, Claude Code, Codex, and other agents.
Install locally
npx @awareness.market/setup --ide cursorNo account, no API key, no credit card. Setup detects Cursor and writes .cursor/rules/awareness.mdc plus the local memory daemon.
The problem
Cursor starts every session from zero.
Every chat starts over
Without retrieval, a new Cursor session has no access to yesterday decisions. The agent asks the same questions and repeats the same mistakes.
Context is trapped in one tool
If the same project is also worked on in Claude Code, Codex, or another IDE, each tool has its own isolated context. Awareness gives them one shared local memory.
How it works
Recall before work. Record after.
Write the rule
Setup writes .cursor/rules/awareness.mdc. The rule tells Cursor to initialize memory at session start, recall before work, and record after a meaningful change.
Recall before work
awareness_recall searches structured knowledge cards, past sessions, and graph facts with hybrid semantic + full-text search. Retrieval runs locally with zero LLM calls.
Record after change
awareness_record captures decisions, fixes, risks, and preferences as structured knowledge, with deduplication and conflict detection.
Awareness injects workflow rules into Cursor's configuration, so the agent initializes memory at session start, recalls before work, and records decisions after every change. Retrieval runs on local SQLite with hybrid semantic + full-text search; it makes zero LLM calls.
What gets remembered
Knowledge, not a transcript.
- Architecture decisions and rejected alternatives
- Bug fixes and failed debugging paths
- Project workflows and conventions
- Pitfalls, risks, and open questions
- Action items and task handoffs
- Reusable skills and agent roles
- Preferences that should follow the project
- Shared context across Cursor and other agents
Compare
Where Awareness fits.
Cursor rules
Best for stable instructions and conventions. Awareness adds dynamic memory and the recall/record loop that rules alone cannot provide.
Basic Memory
A local Markdown knowledge base. Awareness adds workflow-rule injection, 13 knowledge categories, conflict detection, graph memory, and cross-agent recall.
Supermemory / Mem0
Managed memory layers with cloud options. Awareness is local-first by default, keeps data on your machine, and runs retrieval without LLM calls.
Read the comparisonFrequently asked questions
Is Awareness free for Cursor?
Yes. Local-first memory is free forever: unlimited memory libraries, local SQLite, hybrid recall, graph memory, insight extraction, and conflict detection. No account or credit card is required. Optional inference features in the marketplace use credits.
Does Awareness send my Cursor code to the cloud?
No, by default. Memory is stored as human-readable Markdown in your project .awareness directory, with a local SQLite index. Cloud sync is optional and only enabled if you choose it.
How is Awareness different from Cursor rules?
Cursor rules are durable instructions. Awareness is episodic and semantic memory: decisions, workflows, pitfalls, risks, action items, skills, and preferences learned across sessions. It writes a rule that tells Cursor when to recall and record.
How is Awareness different from Basic Memory?
Basic Memory is a local Markdown knowledge base. Awareness adds workflow-rule injection, 13 structured knowledge categories, conflict detection, graph memory, task handoffs, and a shared memory layer across Cursor, Claude Code, Codex, and other agents.
Does the same memory work in Claude Code?
Yes. Awareness is cross-agent: the same local memory can be recalled from Cursor, Claude Code, Codex, Windsurf, Cline, GitHub Copilot, Zed, JetBrains, and other MCP-compatible tools.
How do I verify the Cursor install?
Run npx @awareness.market/setup --ide cursor, then open Cursor and check that the Awareness MCP server is available. The setup writes .cursor/rules/awareness.mdc and starts the local daemon.
Give your agent a memory that compounds.
Local-first, no account, no credit card. Start in 30 seconds and keep the data on your machine.