# GitHub — GitHub intelligence puts your code, context, and history to work

- Company: GitHub (github.com)
- Announced: 2026-10-28T15:40:00+00:00
- Category: capability-change
- Coverage: not counted
- Announcement: yes
- Group: announcements
- Source: https://github.blog/changelog/2026-10-28-github-intelligence-puts-your-code-context-and-history-to-work
- Record: https://forck.live/items/28834-github-intelligence-puts-your-code-context-and-history-to-work
- Subject: Copilot

GitHub is rolling out GitHub intelligence, a context and learning layer built from the graph of GitHub data, so Copilot agents can carry team knowledge between sessions instead of starting fresh. Copilot Memory is now generally available on paid Copilot plans, letting Copilot remember personal preferences and repository conventions across sessions and clients, including the Copilot app, Copilot CLI, VS Code, Copilot cloud agent, Copilot code review, Slack, Teams and GitHub Mobile. Among Copilot CLI sessions reviewed during the public preview where the agent used memory, GitHub says 93% showed better adherence to developer preferences and 42% showed more efficient workflows attributed to the memories included in the session context. Copilot dreaming, now in public preview, reflects on past work to keep that context current through three dream types: personal memory curation, repository customization, and code review customization. Dreaming is opt-in, can add, update and remove personal and repository memories, and proposes changes to checked-in skills and instructions as pull requests for team review; dream runs consume AI credits. GitHub code search lets Copilot find code, configuration, schemas and documentation across related projects and dependencies without a local clone, supporting exact text and symbol search, regular expressions, and semantic search by what code does. Copilot can narrow results by repository, path or language, and the /research command lets it inspect implementations and callers across repositories for tasks such as planning a migration or investigating a bug.

## Evidence

Verbatim from https://github.blog/changelog/2026-10-28-github-intelligence-puts-your-code-context-and-history-to-work:

> Agents should understand more than your codebase—they should understand how your team works. Your preferences, repository conventions, skills, and custom instructions guide how changes should be made, while code in related repositories can show how the pieces fit together. Without that context, agents spend time rediscovering knowledge and can miss your team’s conventions.
> 
> GitHub intelligence is the context and learning layer sourced from the graph of GitHub data. It makes this data useful to agents, helping them remember how you work, keep that guidance current, and find the code and development history relevant to the next task. The goal is for agents to build on what you and your team already know, rather than treating every session as a fresh start.
> 
> That is the advantage of building where your team’s work already lives. A repository memory can capture why an edge case matters and which test covers it. GitHub intelligence allows agents to use that context, with controls over what they can access.
> 
> Three capabilities bring this into your workflow:
> 
> Memory carries knowledge between sessions
> 
> Dreaming keeps the context current
> 
> Code search reaches beyond your checkout.

---

Record: https://forck.live/items/28834-github-intelligence-puts-your-code-context-and-history-to-work
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md