GitHub: Copilot Memory remembers commit style, PR structure and communication preferences across all repositories

GitHub released a significant personalization upgrade for the Copilot ecosystem on May 15, 2026 — Copilot Memory User Preferences. The feature eliminates the developer frustration of repeating the same correction patterns every day (“don’t write conventional commits like that”, “format the PR this way”, “please shorter explanations”) that Copilot has traditionally not remembered between sessions.

Which preference categories does Copilot Memory capture?

GitHub lists three primary categories:

• Commit message style — Conventional Commits format vs free form, average length, language (English, native, mixed), specific syntax (e.g. feat: vs Feature:)
• Pull request structure — which sections the user typically includes (Summary, Test Plan, Breaking Changes), formal or casual header tone, whether a TL;DR is needed
• Communication preferences — formal/casual register, level of detail in explanations (short one-liner vs detailed walkthrough), type of examples the user prefers (code-only vs concept-first)

What does “cross-repo” mean in practice?

Memory works cross-repository — a user’s preferences are learned through interaction in one repo and automatically applied when the user works on others. The practical effect: a developer who works on 5–10 repositories throughout the week does not have to re-correct Copilot each time — preferences follow the user, not the repo.

The approach is the opposite of the per-repo CLAUDE.md model that Anthropic uses for Claude Code, where preferences are tied to the workspace rather than the user. Both models have merits — per-user is convenient for individual developers, per-repo is cleaner for team workflows where different repos have different conventions.

Privacy implications and opt-out

Memory storage is per-user in GitHub’s infrastructure, meaning team members do not share preferences automatically. The feature is opt-in in Copilot settings. Users can review what Memory has recorded and selectively delete individual preferences (e.g. delete a learned commit style when switching project conventions).

Position in the Copilot personalization layer

Memory User Preferences is part of the broader trend where vendor lock-in shifts from “we have a better model” to “we have a better personalization platform”. Cursor 2026 and Codeium have introduced similar adaptive features. GitHub’s advantage is integration with the git workflow — Memory learns from the user’s real git activity, not a synthetic feedback signal.

The announcement fits into a week of dramatic Copilot development releases: Copilot App Technical Preview (14.5.), Copilot Cloud Auto Model (14.5.), Copilot Cloud REST API (13.5.). Cross-repo Memory transforms Copilot from a code completion tool into a personalized development partner that tracks every aspect of the user’s style.