MemScope vs GitHub Copilot Memory
Copilot Memory lets GitHub Copilot learn about a repository and its user. MemScope is a shared memory any MCP client can use.
What GitHub Copilot Memory is
Copilot Memory lets Copilot retain repository-level facts, which are shared with collaborators, and user-level preferences, which follow one person between repositories. Copilot creates memories itself as it works and checks them against the current branch before using them; memories expire after 90 days without reinforcement by default. It is available on all paid Copilot plans and is used across Copilot surfaces such as the Copilot CLI, code review and the cloud agent.
Side by side
Per-person access
GitHub Copilot Memory
Repository-level facts are shared with collaborators who can use Copilot Memory on that repository and are not pooled across repositories. User-level preferences belong to one person. No per-memory audience choice beyond that is documented.
MemScope
Yes. Each person’s agent recalls only memories that person is permitted to see; a deterministic policy decides.
Works across different AI tools
GitHub Copilot Memory
Used across Copilot surfaces (Copilot app, CLI, code review, cloud agent and others). Use by non-Copilot AI tools: not documented.
MemScope
Yes. Claude Code, Cursor, ChatGPT and other MCP clients share one memory.
Sensitivity levels
GitHub Copilot Memory
Not documented.
MemScope
Four levels: Public, Internal, Restricted, Highly restricted. Higher levels need more access.
Audit trail
GitHub Copilot Memory
On Business and Enterprise plans, organization or enterprise administrators can view, export and delete user-level preferences. A general audit trail: not documented.
MemScope
Yes. Every change is audited.
Who writes the content
GitHub Copilot Memory
Copilot writes memories itself as it works; you can also ask it to remember something or import memories with Copilot CLI. Repository-level facts require write access.
MemScope
People and their agents save explicit memories; AI only suggests labels.
Cost
GitHub Copilot Memory
Available on all paid Copilot plans; no separate charge documented.
MemScope
$15 per connected user per month after a 60-day trial with 3 connected users.
Statements about GitHub Copilot Memory come from GitHub Docs: About GitHub Copilot Memory, checked November 2026. “Not documented” means those docs do not say. Products change; check the source. https://docs.github.com/en/copilot/concepts/agents/copilot-memory
When Copilot Memory is enough
- Your team works in GitHub and uses Copilot as its AI tool.
- What Copilot learns about a repository is fine for every collaborator on it to read.
- You prefer memories that Copilot creates and validates itself, without anyone writing them.
In these cases Copilot Memory is enough, and it needs no extra product.
When you need MemScope
- Some knowledge is for one team or project, and should not reach everyone who can read the repository.
- Developers use different AI tools and you want one memory they all read and write.
- You need each change to who can see a memory recorded in an audit log.
Documentation checked November 2026.