If you are using Cursor’s Composer or multi-file agentic edits, you have probably run into this issue:
Composer successfully modifies your backend model or config, but silently leaves your frontend client, documentation, or settings files inconsistent because it doesn’t trace the semantic connection between them. When you start a new composer run or open a new chat, the model has no context on why the previous changes were made.
I built Reponoesis to act as a local, cryptographic semantic memory graph for Cursor.
It runs locally on your machine via a standard stdio MCP server.
Key Benefits for Cursor Users:
-
Context Amnesia Prevention: When you start a new Composer chat, Cursor runs
rpn_get_contextto instantly load all active Architectural Decision Records (ADRs) and concept maps into memory. -
Blast Radius Analysis: Cursor can run
rpn_impact_mapon files before writing edits, ensuring it understands the downstream consequences of mutating a file. -
Deterministic Commit Gating: A local pre-commit hook (
rpn check) blocks git commits if Cursor accidentally introduces logical contradictions or leaves files in a drifted state. -
Agent Write-Back: Cursor uses the
rpn_record_drift_explanationtool to write its own plain-English explanations of drift directly into the local SQLite database, replacing raw cryptographic warnings in the UI.
Quick Setup:
-
Clone the project:
bash
git clone https://github.com/adithya/reponoesis.git
cd reponoesis
npm install && npm run build
cd packages/cli && npm link && cd ../mcp && npm link
-
Navigate to your project folder, run
rpn initandrpn scan. -
Add the server to your Cursor MCP settings:
-
Name:
reponoesis -
Type:
command -
Command:
rpn-mcp --project /absolute/path/to/your/project
-
I’ve made the repository public on GitHub: MathewAddala/reponoesis
Would love to get your feedback on using this to make Cursor agent runs safer and more context-aware.


