What's Changed

Copilot Memory is now enabled by default for all GitHub Copilot Pro and Copilot Pro+ individual users. Previously available as an opt-in public preview feature, this change means developers will automatically benefit from persistent, repository-level context without taking action.

How Copilot Memory Works

Copilot Memory enables agents to discover and store useful facts about repositories—including coding conventions, architectural patterns, and critical cross-file dependencies—and reuse that knowledge in future interactions. Key characteristics:

• Repository-scoped: Memories are strictly limited to a single repository and validated against the current codebase before use, preventing stale or inaccurate context
• Auto-expiration: Memories automatically expire after 28 days to keep information fresh
• Cross-agent sharing: Knowledge discovered by the coding agent benefits code review and CLI workflows immediately

Where Memory is Applied

Copilot Memory works across three primary tools:

• Copilot coding agent: Applies repository-specific context when implementing tasks and opening pull requests
• Copilot code review: Uses learned patterns to provide more accurate, targeted review feedback
• Copilot CLI: Brings repository awareness to terminal workflows

User Control and Management

Individual users can disable Copilot Memory anytime via personal settings at Copilot Settings > Features > Copilot Memory. Repository owners can review and delete stored memories under Repository Settings > Copilot > Memory. Enterprise and organization admins retain full control over memory availability through Copilot policies at the enterprise and organization levels.

For detailed guidance, see the official documentation on Copilot Memory and enabling and curating memories.