GitHub Copilot Memory is generally available on paid Copilot plans
GitHub made GitHub Copilot Memory available on paid Copilot plans. It retains personal preferences and repository conventions across sessions and clients. Personal records can be viewed and deleted in settings.
GitHub announced the general availability of GitHub Copilot Memory on paid Copilot plans. Memory allows personal preferences and repository conventions to be retained across sessions and clients. Records can be created in the Copilot app, Copilot CLI, VS Code, Copilot cloud agent and Copilot code review, as well as in Slack, Teams and GitHub Mobile.
Copilot sessions automatically create and manage memory records. For example, a user can ask Copilot to remember a preferred opening for pull request descriptions. Repository memory can retain the correct command for running tests or team requirements for reviewing work. Personal records can be viewed and deleted in Copilot settings.
According to GitHub, during public testing, 93 % of evaluated Copilot CLI sessions using memory showed better adherence to developer preferences, and 42 % showed more efficient workflows attributed to memory records in the session context. These are results from company evaluations of selected sessions, rather than independently confirmed benefits for all users.
Why it matters
Memory may reduce the need to repeat the same instructions when starting a new session or switching clients. Its practical benefit depends on whether the saved records accurately capture preferences and working rules; the reported percentages alone do not establish time or financial savings.
Two audiences, two different impacts
What this means
For individuals
A user on a paid Copilot plan can carry their working preferences across sessions and clients while also reviewing saved personal records.
For a business
In enterprise development, repository memory can repeatedly supply the correct test commands and team requirements for reviewing work, which may reduce the need to explain procedures again.
DevelopmentCheck the original
Event sources
clearly official source · 1 publisher, 0 independent. We count feeds from the same owner only once.