Copilot Memory adds deletion, scope, and CLI controls
GitHub Copilot Memory has introduced enhanced controls for memory deletion and scope, alongside expanded capabilities within the Copilot CLI. These updates aim to provide users with greater management over their Copilot data and usage. The feature is currently in public preview and available to users now.
- →Repository-level off switch for Copilot Memory
- →Improved memory deletion and scope controls
- →Expanded Copilot CLI memory management
- →Copilot Memory is in public preview
Features (1) ›
- Repository-level off switch for Copilot Memory
A new repository-level off switch has been added, enabling users to easily disable Copilot Memory for specific repositories.
Enhancements (2) ›
- Improved memory deletion and scope controls
Copilot Memory now offers improved controls for deleting memory and managing its scope. This allows users greater flexibility in managing their Copilot data.
- Expanded Copilot CLI memory management
Further memory controls have been integrated into the Copilot CLI, providing command-line users with more options for managing Copilot Memory.
Notes (1) ›
- Copilot Memory is in public preview
Copilot Memory is currently available in public preview, indicating that it is an early-access feature for users to try and provide feedback on.
https://github.blog/changelog/2026-05-26-copilot-memory-has-more-controls-for-deletion-scope-and-the-copilot-cli
Related releases
- GitHub Copilot Deprecates Gemini 2.5 Pro and 3 Flash Models GitHub Changelog ·
- GitHub Copilot Enterprise Teams Model Policy Targeting in Public Preview GitHub Changelog ·
- npm restricts granular access token ability to bypass 2FA for sensitive actions GitHub Changelog ·
- GitHub Models officially retired GitHub Changelog ·
- GitHub Copilot VS Code Updates: Agents, Chat, UI, and Accessibility GitHub Changelog ·
- GitHub Actions: Reference same-repo workflows with self-repository syntax GitHub Changelog ·