GitHub Copilot with Memory Bridge

GitHub Copilot with memory beyond a single repository

Connect GitHub Copilot 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.

Say it in ChatGPT, carry on in GitHub Copilot

ChatGPT
You

In all our APIs: field names in snake_case, dates in ISO 8601.

ChatGPT

Saved.

Saved to memory · API convention
One memory
GitHub Copilot
You

Create a new endpoint that returns invoices.

With Memory Bridge

Created. Fields are snake_case and dates ISO 8601, following your saved API convention.

From memory · API convention

Illustrative example

What does GitHub Copilot remember on its own?

Copilot reads an instructions file in the repository and has memory scoped to the repository it works in. What it knows about one project does not carry to another.

We reviewed this description in October 2026. These tools change often, so check the official help page for current details.

What does Memory Bridge add?

Conventions that hold across all your repositories: naming, test policy, what you agreed with the client. Written once and read by Copilot in every project.

Connect GitHub Copilot in three steps

  1. 1

    Add Memory Bridge

    Open Copilot settings in your editor and add Memory Bridge under external tools.

  2. 2

    Sign in and pick your projects

    Choose which projects it can reach, and whether it reads only or reads and writes.

  3. 3

    Carry on working

    Ask GitHub Copilot as you always do. It finds what your request needs in your memory.

Common questions

Does Memory Bridge replace GitHub Copilot's own 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.

Do I need a paid GitHub Copilot plan?

Connecting outside services in GitHub Copilot may be limited to certain plans or versions. Check the tool's official help page.

What can GitHub Copilot see of my memory?

Only the projects you allowed, with the permission you chose. You can disconnect it at any time.

What if the connection fails?

We have tested this connection and it works. If you hit a problem, write to us through the support channel with the error message.

Keep reading

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

Rules say how you write code. Connect Cursor to Memory Bridge and stop re-explaining your work.

Claude Code

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.

One memory. Every tool you use.

The trial is invite-only for now. Request access and we will write to you when your seat opens.