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.
Kiro with Memory Bridge
Connect Kiro 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.
The client ruled out social sign-in. Sign-in is by mobile number and one-time code only.
ChatGPTSaved.
Saved to memory · Client requirementsWrite the spec for the sign-in feature.
With Memory BridgeSpec written for mobile number and one-time code only. I left out social sign-in because the client ruled it out.
From memory · Client requirementsIllustrative example
Kiro works from specs and steering files inside the project. They describe what to build, not the discussion that came before.
We reviewed this description in October 2026. These tools change often, so check the official help page for current details.
The discussion before the spec: what the client asked for, what was ruled out and why. Kiro reads it while writing the spec, so you do not explain it again.
Open Kiro settings and add Memory Bridge under external services.
Choose which projects it can reach, and whether it reads only or reads and writes.
Ask Kiro 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 Kiro 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.
Rules say how you write code. Connect Cursor to Memory Bridge and stop re-explaining your work.
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.
The trial is invite-only for now. Request access and we will write to you when your seat opens.