Memory for coding agents
Instruction files tell a coding agent how to write code. How to give coding tools a memory of decisions and reasons that lasts across sessions and tools.
Cursor with Memory Bridge
Connect Cursor to Memory Bridge once and it reads from, and writes to, the memory of your work. What you save here is there in your other tools.
We rejected moving to a managed database service: three times the cost. Revisit at 50,000 users.
ClaudeSaved.
Saved to memory · Database decisionSuggest a way to take load off the database.
With Memory BridgeI suggest a read replica and caching for the heavy queries. I left out the managed service because you rejected it on cost, with a review at 50,000 users.
From memory · Database decisionIllustrative example
Cursor relies on rules files inside the project and on memories it builds from your chats with it. Both are tied to the project and to Cursor.
We reviewed this description in October 2026. These tools change often, so check the official help page for current details.
Rules say how you write code. Your memory says why you decided it. Architecture decisions and their reasons live in one place, read by Cursor and any other tool you use.
Open Cursor settings and add Memory Bridge under tools and external services.
Choose which projects it can reach, and whether it reads only or reads and writes.
Ask Cursor as you always do. It finds what your request needs in your memory.
No. Your project instruction files stay where they are and keep doing their job. Memory Bridge adds what does not fit in those files and makes it available to your other tools.
Connecting outside services in Cursor may be limited to certain plans or versions. Check the tool's official help page.
Only the projects you allowed, with the permission you chose. You can disconnect it at any time.
We have tested this connection and it works. If you hit a problem, write to us through the support channel with the error message.
Instruction files tell a coding agent how to write code. How to give coding tools a memory of decisions and reasons that lasts across sessions and tools.
Connect GitHub Copilot to Memory Bridge and it reads from the memory of your work. What you save in GitHub Copilot is there in your other AI tools.
Connect Claude Code to Memory Bridge and it reads from the memory of your work. What you save in Claude Code is there in your other AI tools.
The trial is invite-only for now. Request access and we will write to you when your seat opens.