GitHub Copilot app + agimem
Give every GitHub Copilot app session persistent memory.
The GitHub Copilot app is a desktop app for running and steering coding agents across your repositories. With agimem, those sessions can share your conventions, architecture decisions, and debugging notes instead of each one starting from scratch. Connect agimem as an MCP server and the same memory is available across your sessions and other AI tools.
Setup in 4 steps
Create a Capsule on agimem
Sign up at agimem.dev and create a Capsule from the dashboard. Each Capsule is an isolated memory space — create one per project or one for all your work.
Generate an API key
Click your Capsule and generate an API key. It starts with agm_ — copy it now, you won't see it again.
Add the MCP server to your Copilot config
Open ~/.copilot/mcp-config.json, creating it if needed, and paste the configuration below with your API key. If the file already has servers, add the agimem entry alongside them.
Start using memory
Start a new session and ask Copilot to remember something, then verify it persists in another session. To manage installed servers, open Customize in the sidebar and click Installed.
Fastest way: paste a prompt
Give this prompt to your GitHub Copilot app agent and it will configure everything automatically:
Agent prompt
Set up agimem as my memory server: https://agimem.dev/setup
Manual configuration
Add this to your Copilot configuration file. Servers configured for Copilot CLI are automatically available in the GitHub Copilot app, so this one file covers both:
~/.copilot/mcp-config.json
{
"mcpServers": {
"agimem": {
"type": "http",
"url": "https://agimem.dev/api/mcp",
"headers": {
"Authorization": "Bearer agm_your_api_key"
},
"tools": ["*"]
}
}
}What your agent can do with agimem
- Store and recall coding conventions
- Remember project architecture across sessions
- Share context between multiple agents
- Keep research notes and findings persistent
- Track preferences and writing style
- Maintain state for long-running automations
- Organize memories with tags
- Set time-to-live for temporary data
Frequently asked questions
Can I add agimem from inside the app?
You can try it from Customize → MCP by adding a custom server with the URL and Authorization header shown above. If the form doesn't offer a place for the header, use the config file instead.
Do I need to set this up again for Copilot CLI?
No. Copilot CLI reads ~/.copilot/mcp-config.json directly, so adding agimem there covers both the CLI and the app.
Can I use a different Capsule per repository?
Yes. Repository-level MCP configuration, such as a .mcp.json file, takes precedence over your user configuration when the server names match. Keep real API keys out of version control.
Does this replace Copilot's GitHub tools?
No. agimem adds memory tools alongside whatever else your Copilot sessions can use, and the same Capsule can be shared with your other MCP clients.
Ready to get started?
Create a free Capsule and connect GitHub Copilot app.