GitHub's October 28 announcement describes GitHub intelligence as a context layer for Copilot. It combines saved preferences, repository guidance, and code search across related projects so a session does not always begin without team context.
Availability is not the same for every feature
- Copilot Memory is generally available on paid plans and can retain personal preferences and repository conventions.
- Copilot dreaming, which can propose or update context, is in public preview and is opt-in.
- Code search can reach related repositories, with access controlled by the connected account and available repositories.
The announcement says repository instruction changes from dreaming are proposed for review rather than silently committed. Administrators and users should still inspect what context is stored and which repositories an agent can access.
Persistent context can reduce repeated setup, but stale or overbroad instructions can also mislead an agent. Review and remove memories that no longer describe how a project works.