GitHub Copilot Memory 正式 GA:跨会话保留仓库约定与个人偏好
GitHub Copilot Memory 已在付费方案正式可用,可在 CLI、VS Code、云端代理等多端保留个人偏好与仓库约定;同步公开预览的 dreaming 会以 PR 提议修改 Skills,并消耗额度。
面向编码智能体与编辑器场景,跨会话“记住团队约定”正在从口头习惯变成产品能力。
据 @CityzenHyd 对 GitHub 变更日志的整理(帖文约 2026-10-29),GitHub Copilot Memory 已在付费 Copilot 方案上 正式一般可用(GA)。Memory 可在多次会话、多种客户端之间保留个人偏好与仓库级约定,覆盖范围包括应用端、CLI、VS Code、云端代理、代码审查,以及 Slack、Teams 与移动端。
仓库级 Memory 可存放例如“正确的测试命令”、团队期望代理如何自检等约定,从而减少每个新会话重复粘贴同一段指引。预览阶段 GitHub 给出的内部复盘数字是:在代理实际使用了 Memory 的 Copilot CLI 会话中,约 93% 更贴合开发者偏好,约 42% 工作流更高效;原帖明确这些比例来自 GitHub 对预览会话的自有复盘,不是外部独立基准。
同期进入 公开预览 的还有 dreaming:它会回顾历史会话以整理记忆,并把对已入库 Skills、自定义指令文件的修改建议以 Pull Request 形式提出,而不是直接改仓库。原帖提醒:dreaming 需主动选择启用,管理员要在 Copilot 策略里打开,且每次 dream 运行会消耗 AI 额度。
对已在多端使用 Copilot / 编码代理的团队,Memory 的价值主要是把“项目规矩”从聊天上下文提升为可复用的共享记忆;引入 dreaming 前应先确认策略开关与额度预算。原帖未展开:各套餐具体配额、Memory 的存储位置与保留期限、以及企业数据驻留选项。
GitHub Copilot Memory Generally Available Across Paid Plans and Clients
GitHub Copilot Memory is now generally available on paid Copilot plans, according to the GitHub changelog.
Copilot can keep personal preferences and repository conventions across sessions and clients: the app, CLI, VS Code, cloud agent, code review, Slack, Teams and Mobile.
A repository memory can hold things like the right test command or how the team expects the agent to check its work, so the same guidance stops getting repeated every session.
The numbers GitHub gives come from the preview: among Copilot CLI sessions where the agent used memory, 93% showed better adherence to developer preferences and 42% showed more efficient workflows.
Alongside it, "dreaming" entered public preview. It reviews past sessions to curate memories, and it proposes edits to checked-in skills and custom instruction files as pull requests instead of changing them directly.
Caveat: dreaming is opt-in, admins have to enable it through Copilot policies, and every dream run consumes AI credits. The 93% and 42% figures are GitHub's own review of preview sessions, not an external benchmark.