Copilot Memory Gets Deletion Controls, Repo Toggle, CLI Commands
Copilot Memory now lets repo admins toggle it off, adds CLI commands for control, and clarifies whether memories are personal or shared. Better deletion guidance too.
TL;DR
- Copilot Memory now has a repository-level off switch for admins
- New
/memorycommands in the Copilot CLI to toggle and check status - Clearer scope labeling when storing memories (user vs. repository level)
- Better deletion guidance when you ask Copilot to forget something
New
- Repository-level off switch — Admins can disable Copilot Memory per repo in Copilot settings; existing facts aren't deleted, user preferences stay intact
/memoryCLI commands — Use/memory on,/memory off, and/memory showin the Copilot CLI; settings persist across sessions- Scope clarity at capture — The
store_memorypermission prompt now explicitly labels whether a memory is user-level (you only) or repository-level (all contributors) - Deletion guidance — When you ask Copilot to forget something, it directs you to the right place to remove it and down-votes the memory where voting exists
Managing Your Memories
- User-level preferences: Review or delete in your Copilot Memory settings
- Repository facts: Owners can review, delete, or disable Copilot Memory under Repository Settings > Copilot > Memory
Copilot Memory is in public preview and available to all paid Copilot plans. Learn more about Copilot Memory or share feedback in GitHub Community.
Source: GitHub Changelog