GitHub rolls Copilot Memory into preview

GitHub on June 2 put Copilot Memory support for user preferences into public preview for Copilot Business and Enterprise customers, adding a personalization feature with administrative and privacy controls. The update was disclosed in a GitHub changelog post dated June 2. GitHub said the feature lets Copilot persist user preferences, while giving organizations tools to control how the capability is deployed. The release adds another enterprise-focused control layer as GitHub expands Copilot features beyond code completion. ### What exactly did GitHub put into preview? GitHub said Copilot Memory now supports user preferences for Business and Enterprise accounts in public preview. According to the company’s June 2 changelog post, the feature allows Copilot to retain user preferences over time rather than treating each interaction as isolated. The June 2 changelog entry said the update includes support for persisted preferences, administrative controls, role-based scopes, rollout options and account-level privacy settings. GitHub framed the release as available to Copilot Business and Copilot Enterprise customers. ### Which customers get the feature first? (github.blog) Business and Enterprise customers are the initial users named in GitHub’s June 2 announcement. The changelog post specifically describes the release as a public preview for those account types, rather than for individual Copilot Pro users or the broader GitHub user base. (github.blog) GitHub has used staged rollouts for other recent Copilot features. In a separate June 2 changelog post, the company said the GitHub Copilot desktop app’s technical preview was expanded to existing Copilot Pro, Pro+, Business and Enterprise customers, showing that GitHub is broadening access to multiple Copilot products in phases. (github.blog) ### What controls did GitHub say administrators will have? GitHub said administrators will have controls tied to rollout, scope and privacy. The June 2 changelog post said the feature includes admin controls, role-based scopes and rollout options, indicating companies can decide how broadly Memory is enabled and for whom inside an organization. (github.blog) Account-level privacy settings are also part of the preview, according to GitHub’s post. GitHub did not, in the changelog entry available for this report, spell out every implementation detail of those settings, but it did identify privacy controls as part of the package for Business and Enterprise customers. (github.blog) ### How does this fit with GitHub’s other Copilot updates this week? June 2 was also the date of other GitHub Copilot announcements. GitHub published changelog posts the same day saying the Copilot SDK had reached general availability and that the GitHub Copilot desktop app’s technical preview had been expanded. Those announcements place the Memory preview alongside a broader set of product updates around Copilot’s tooling and access. (github.blog) GitHub described the desktop app separately as an “agent-native desktop experience” in a company blog post, while the changelog said that preview had expanded across Windows, macOS and Linux for existing Pro, Pro+, Business and Enterprise customers. The Memory announcement is narrower, focusing on enterprise personalization controls. (github.blog) ### What happens next for customers watching the feature? The next concrete milestone is the public preview period now underway for Copilot Business and Enterprise accounts. GitHub’s June 2 changelog post is the company’s published reference point for availability, feature scope and rollout details for administrators evaluating the Memory setting. (github.blog)