Copilot Memory Now Default Behavior

GitHub has moved Copilot Memory from an opt-in preview feature to default-enabled status for all Copilot Pro and Copilot Pro+ subscribers. This persistent, repository-level knowledge system enables Copilot to understand and reuse context about codebases, reducing friction in development workflows.

How It Works

Copilot Memory discovers and stores facts about repositories—including coding conventions, architectural patterns, and cross-file dependencies—and applies this knowledge in future interactions. Memories are scoped strictly to individual repositories and validated against the current codebase before use, ensuring stale or inaccurate context is never applied. Memories automatically expire after 28 days to stay fresh.

The feature works seamlessly across three Copilot interfaces:

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

Since memories are shared across agents, knowledge discovered in one context (e.g., coding) immediately benefits others (e.g., code review).

User Control and Administration

No action is required—Pro and Pro+ users benefit immediately. Users who prefer to disable the feature can do so in personal Copilot settings under Features > Copilot Memory. Repository owners can review and delete stored memories anytime in Repository Settings > Copilot > Memory. Enterprise and organization admins retain full control via Copilot policies at the enterprise and organization levels.