GITHUB COPILOT ADDS CROSS-AGENT, REPO-SCOPED MEMORY (PUBLIC PREVIEW)
GitHub released an opt-in cross-agent memory for Copilot that lets coding, CLI, and code review agents retain repository-scoped context for 28 days with real-ti...
GitHub released an opt-in cross-agent memory for Copilot that lets coding, CLI, and code review agents retain repository-scoped context for 28 days with real-time citation checks. One report claims A/B tests showed a 7% higher pull-request merge rate and a small uptick in positive code review feedback; the feature is in public preview for paid plans.
Shared, expiring repo memory can reduce review churn and handoffs by preserving context across tools.
Repo-scoped and time-bounded memory offers a clearer privacy model for regulated teams.
-
terminal
Pilot on a few services: enable memory and track PR merge rate, time-to-merge, review comment acceptance, and rework rates.
-
terminal
Validate data boundaries and auditability: confirm memory stays repo-scoped, expires after 28 days, and citations map to source code or docs.
Legacy codebase integration strategies...
- 01.
Roll out opt-in on low-risk repos and update contributor guidelines to capture safe 'memory-worthy' facts without secrets.
- 02.
Review CI/policy interactions so agent suggestions do not bypass required checks, codeowners, or security gates.
Fresh architecture paradigms...
- 01.
Bake memory usage into repo templates (runbooks, feature flags, domain glossary) and standardize how agents write and cite notes.
- 02.
Define governance early: retention policy, access controls, and prompts for code review agents to reference memory consistently.