Copilot Memory is now enabled by default for all GitHub Copilot Pro and Copilot Pro+ users.
Previously in public preview as an opt-in feature, Copilot Memory allows Copilot to build and retain a persistent, repository-level understanding of your codebase so you spend less time reexplaining context and more time shipping code.
What is Copilot Memory?
Copilot Memory enables Copilot agents to discover and store useful facts about a repository (e.g., coding conventions, architectural patterns, and critical cross-file dependencies) and reuse that knowledge in future interactions. Memories are strictly scoped to a single repository and validated against the current codebase before being applied, so stale or inaccurate context is never used. To keep things fresh, memories automatically expire after 28 days.
Once enabled, Copilot Memory works across:
- Copilot coding agent: Applies repository-specific context when implementing tasks and opening pull requests.
- Copilot code review: Uses learned patterns to give more accurate, targeted review feedback.
- Copilot CLI: Brings repository awareness directly to your terminal workflow.
Because memories are shared across agents, knowledge discovered by the coding agent can immediately benefit code review and vice versa.
What’s changing
Copilot Memory is now on by default for individual users on Copilot Pro and Copilot Pro+ plans. No action is required to start benefiting from it.
If you prefer to opt out, you can disable Copilot Memory at any time in your personal Copilot settings under Features > Copilot Memory.
Enterprise and organization admins retain full control over memory availability for their members via Copilot policies at the enterprise and organization levels.
Managing memories
Repository owners can review and delete stored memories at any time under Repository Settings > Copilot > Memory.
For more information, see About agentic memory for GitHub Copilot and Enabling and curating Copilot Memory.
Join the Community discussion to share your feedback.
Editor’s note (March 4th, 2026): Updated the Community discussion link.