Copilot Memory is generally available on paid plans, and "dreaming" enters public preview: it curates memories and proposes instruction changes through pull requests
Agents now remember personal preferences and repository conventions across sessions and clients, while team-level changes still go through review.
// Key points
- Memories can be created in the Copilot app, CLI, VS Code, cloud agent, code review, Slack, Teams and GitHub Mobile, and are reused across sessions and clients.
- Among Copilot CLI sessions in the public preview where memory was used, 93% showed better adherence to developer preferences and 42% showed more efficient workflows.
- Dreaming reflects on past work: it curates personal and repository memories, proposes changes to skills and custom instruction files as pull requests, and turns recurring accepted review feedback into code review guidance; runs consume AI credits.
- Copilot can also search code across repositories in an organization through /research, including regex and semantic search.
Builder's takeRouting instruction-file changes through pull requests is the right line: memory that changes how a whole team works should be reviewable like code. I would turn on repository memory but hold dreaming PRs to the same review as any code, and skim personal memories now and then, because stale memories turn into silent wrong defaults.
// Background · from #Coding agents
Full timeline →- Oct 29 GitHub Copilot Fusion is generally available: it routes and orchestrates models per task, scoring 60 on the Coding Agent Index at about half the API cost per task
- Oct 29 GitHub Agentic Workflows is generally available: write automation in Markdown, compile it to Actions YAML, and run it with Copilot or your own coding agent
- Oct 29 GitHub Enterprise now includes Copilot for every licensed user, with AI usage metered from the first request against the enterprise budget