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

By Steven Van · 2026-10-28

Copilot Memory is generally available on paid plans, and Dreaming enters preview on eligible paid plans, needing GPT-6.1 Sol and billed in AI credits.

Copilot Dreaming is in preview for eligible paid Copilot plans, alongside [GitHub](<https://creatorstoolbox.com/tools/github>)'s general availability of Copilot Memory. Both are part of what [GitHub calls GitHub intelligence](<https://docs.github.com/copilot/concepts/prompting-and-context/copilot-dreaming?utm_source=gh-intelligence-changelog-dreaming-billing-docs&utm_medium=changelog&utm_campaign=universe-2026#availability-and-prerequisites>), a context and learning layer built from the graph of GitHub data. It is meant to help agents remember how a team works, keep that guidance current, and find relevant code and history.

## Three capabilities

- **Memory** carries knowledge between sessions. It is now generally available on paid Copilot plans.

- **Dreaming** keeps the context current.

- **Code search** reaches beyond your checkout.

Availability and settings vary by capability.

## Memory

Copilot can remember personal preferences and repository conventions across sessions and clients. Memories can be created in the Copilot app, Copilot CLI, VS Code, Copilot cloud agent, Copilot code review, Slack, Teams and GitHub Mobile. A user can tell Copilot to "Remember to start my pull request descriptions with a TL;DR", and the preference is reused across Copilot experiences. Repository memories can record the right test command or how the team expects Copilot to check its work.

Copilot sessions also generate and curate memories on their own. GitHub says that among Copilot CLI sessions reviewed during the public preview where the agent used memory, 93% showed better adherence to developer preferences and 42% showed more efficient workflows.

## Dreaming: availability and prerequisites

Dreaming is available for eligible paid Copilot plans. The initial preview requires access to GPT-6.1 Sol and is not available on Copilot Pro. It does not support GitHub Enterprise Cloud with data residency. All capabilities need an eligible Copilot subscription and permission under enterprise and organization policies.

- **Repository customization:** repository-level Memory enabled, Dreaming enabled through organization policy or the personally owned repository's settings, session syncing, and GPT-6.1 Sol allowed by policy.

- **Personal memory curation:** personal Memory enabled, personal Dreaming permitted by managed policies where applicable and enabled for the user, session syncing, and GPT-6.1 Sol allowed by policy.

- **Code review customization:** repository-level Memory enabled, Dreaming enabled as for repository customization, Copilot code review and its preview features enabled, and GPT-6.1 Sol allowed by policy. Session syncing is not required. Self-hosted runners are not currently supported.

Each Dreaming setting turns on the capabilities whose prerequisites are met within its scope, and they cannot be switched on or off individually. If Dreaming is already on when additional prerequisites are completed, it needs to be turned off and on again to activate them.

## Session syncing

Session syncing saves local sessions to a GitHub account. It is on by default for Copilot CLI and the GitHub Copilot app, subject to policy. For users who get Copilot through an enterprise or organization, the "Store local sessions in the Cloud" policy under "Copilot CLI" must be set to at least View from cloud, otherwise sessions stay local. Anyone who set remoteExport to false in ~/.copilot/settings.json needs to remove it or set it to true to restore syncing.

## Costs

Dreaming usage is billed in AI credits as part of existing Copilot usage, not as a separate item. Every run uses credits, including runs that make no changes or process inactive repositories. Cost depends on processing and the number of enabled users and repositories. GitHub advises reviewing repository coverage and billing controls first. Alerts alone do not stop usage, a per-user budget may not cover repository-level app usage, and separate budgets for individual Dreaming app installations are not available.

## Data and controls

Dreaming can use previously synced sessions, memories, repository content and pull request review feedback. Instructions and skills it proposes arrive as pull requests, visible to people with access to the repository. To stop future runs, disable Dreaming in the relevant enterprise, organization, personal or repository settings (at enterprise level, select Disabled everywhere). Turning off personal Dreaming does not stop runs for organization-owned repositories. Disabling it does not undo changes, delete created information, close pull requests or restore deleted memories, and run details in the Copilot app are not a complete history and have no undo.

![GitHub](<https://github.githubassets.com/assets/GitHub-Mark-ea2971cee799.png>)

GitHub

Where the world builds software — Git hosting, pull requests, issues, Actions CI/CD, and Copilot, free for public and private repos.

[View GitHub →](<https://creatorstoolbox.com/tools/github>)

Sources

[Original source](<https://github.blog/changelog/2026-10-28-github-intelligence-puts-your-code-context-and-history-to-work>)

[Read GitHub intelligence puts your code, context, and history to work on Creators Toolbox](<https://creatorstoolbox.com/blog/github-github-intelligence-puts-your-code-context-and-history-to-work>)

---
Canonical source: https://creatorstoolbox.com/blog/github-github-intelligence-puts-your-code-context-and-history-to-work
