Improvement
Copilot Memory now includes improved memory deletion, adds a repository-level off switch, and brings further memory controls into the Copilot CLI. Copilot Memory is in public preview and available to all paid Copilot plans.
What’s changing
Deletion guidance: When you ask Copilot to forget something, it now points you to the right place to remove the memory and down-votes the memory where voting is available.Repository-level off switch: Repository admins can now disable Copilot Memory for a repository from the existing Copilot feature controls in repository settings. Repository-level facts will no longer be stored or read. Preexisting facts are not deleted. User-level preferences are unaffected.Use/memory
command in the Copilot CLI:/memory on
to enable Copilot Memory,/memory off
to disable it, and/memory show
to check its current status. Your choice persists across sessions.Clearer scope at capture time: Thestore_memory
permission prompt now explicitly states whether the entry will be auser-level preference(i.e., visible only to you, used in your sessions across repositories) or a** repository-level fact**(i.e., visible to all contributors on the repository).
Managing memories Your user-level preferences: Review or delete them in your personalCopilot Memory settings.Your repository’s facts: Repository owners can review, delete, or turn off Copilot Memory for the repository underRepository Settings > Copilot > Memory.
Learn more about [managing stored memories](https://docs.github.com/copilot/how-tos/use-copilot-agents/copilot-memory#viewing-and-deleting-repository-level-facts-and-user-level-preferences).
[Share your feedback](#share-your-feedback)
For more information, see [About GitHub Copilot Memory](https://docs.github.com/copilot/concepts/agents/copilot-memory).
We’re continuing to evolve Copilot Memory and plan to bring it to more features in the future. To share feedback or join the discussion, visit the GitHub Community.