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.
Goose with Memory Bridge
Connect Goose 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 staging environment is refreshed from production every night, so we keep no permanent test data there.
ChatGPTSaved.
Saved to memory · Staging environmentPrepare data to test the reports feature.
With Memory BridgeI wrote a script that creates the test data on each run, because staging is wiped nightly and cannot hold permanent data.
From memory · Staging environmentIllustrative example
Goose reads a hints file in the project and has a memory extension that keeps what you ask on your machine. It belongs to Goose and to that machine.
We reviewed this description in October 2026. These tools change often, so check the official help page for current details.
Memory that does not live on one machine. What you saved at your desk is there on your other computer, and in your other tools.
Open Goose settings and add Memory Bridge under extensions.
Choose which projects it can reach, and whether it reads only or reads and writes.
Ask Goose 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 Goose 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.