GitHub Copilot IDE 弃用旧 Agent 上报：VS Code 1.139.0
Update your IDE to restore agent activity in Copilot usage metrics
这是一次破坏性的指标采集变更，直接导致依赖 Copilot 数据进行效能评估的读者出现数据断层。虽然不收费，但历史数据不可回溯，且涉及 VS Code、JetBrains 等多款核心开发工具的版本升级。建议立即检查团队 IDE 版本，在 11 月前完成迁移以避免长期数据失真。
If your Copilot usage metrics have shown agent activity or agent lines of code falling while Copilot usage kept growing, we’ve found the cause, and a fix is rolling out to each IDE. Several IDEs recently moved Copilot agent sessions to the Copilot SDK. Those sessions didn’t identify which IDE they came from, so usage metrics couldn’t attribute them correctly. Most of that activity was left out of reports, and some was counted as Copilot CLI activity. Only IDE versions that use the Copilot SDK for agent mode are affected. Developers on earlier versions are still counted.
如果您的 Copilot 使用指标显示，在 Copilot 使用量持续增长的同时，智能体活动或智能体代码行数却在下降，我们已找到原因，并且修复程序正在向各个 IDE 推送。最近，几个 IDE 将 Copilot 智能体会话迁移到了 Copilot SDK。这些会话无法标识其来源 IDE，因此使用指标无法正确归因。大部分此类活动被排除在报告之外，部分则被错误地计为 Copilot CLI 活动。只有使用 Copilot SDK 进行智能体模式的 IDE 版本受到影响。早期版本的开发者仍会被正常统计。
The fix is available now in Visual Studio Code. Other IDEs will receive it in upcoming releases, which we expect to finish rolling out by November 2026. Once developers update, their agent activity is counted again in the Copilot usage metrics dashboard and API.
该修复程序现已在 Visual Studio Code 中可用。其他 IDE 将在即将到来的版本中获得此修复，我们预计将在 2026 年 11 月前完成全面推送。一旦开发者更新，他们的智能体活动将在 Copilot 使用指标仪表板和 API 中重新被统计。
Update your IDE
更新您的 IDE
Agent activity is counted again once developers are on these versions. If your developers are on an affected version, update as soon as the fixed version is available, because their activity can’t be recovered later. If you manage IDE versions centrally and rely on agent metrics, you can plan your rollout to move developers directly to these versions.
当开发者升级到这些版本后，智能体活动将重新被统计。如果您的开发者使用的是受影响的版本，请在修复版本可用时尽快更新，因为之前的活动数据无法后续恢复。如果您集中管理 IDE 版本并依赖智能体指标，可以规划您的推送策略，直接将开发者迁移到这些版本。
| IDE | Version | Availability |
|---|---|---|
| Visual Studio Code | 1.139.0 and later | Available now |
| Visual Studio | 18.12 | Not yet released, expected in October 2026 |
| JetBrains IDEs | Next plugin release | Not yet released, expected by late October 2026 |
| Eclipse | Next plugin release | Not yet released, expected by November 2026 |
| Xcode | Next plugin release | Not yet released, expected by November 2026 |
| IDE | 版本 | 可用性 |
|---|---|---|
| Visual Studio Code | 1.139.0 及更高版本 | 现已可用 |
| Visual Studio | 18.12 | 尚未发布，预计 2026 年 10 月推出 |
| JetBrains IDEs | 下一个插件版本 | 尚未发布，预计 2026 年 10 月底推出 |
| Eclipse | 下一个插件版本 | 尚未发布，预计 2026 年 11 月推出 |
| Xcode | 下一个插件版本 | 尚未发布，预计 2026 年 11 月推出 |
We’ll add each version to the supported IDEs in the docs as it ships.
随着各版本正式发布，我们将把它们添加到文档的支持 IDE 列表中。
What to expect in your reports
报告中会出现的情况
- Billing isn’t affected. This issue only changed how agent activity was attributed in usage metrics, not what you were charged.
- The gap persists for any developer on an affected IDE version until they update. Until then, their agent interactions and agent lines of code (e.g., loc_added_sum and loc_deleted_sum for agent_edit) stay undercounted. This applies to enterprise, organization, and user reports, for both 1-day and 28-day reports.
- We can’t backfill missing data. Activity from affected IDE versions doesn’t identify which IDE it came from, so it can’t be attributed after the fact. Expect a gradual recovery as developers move to these versions rather than a single jump.
- Copilot CLI metrics may be inflated, because some activity from other SDK-based clients was counted as Copilot CLI activity. This will clear up as developers update those clients, but earlier Copilot CLI metrics can’t be corrected, because that activity can’t be separated from real Copilot CLI use. Copilot CLI users don’t need to update.
- 计费不受影响。此问题仅改变了使用指标中智能体活动的归因方式，并未改变您的收费内容。
- 对于任何使用受影响 IDE 版本的开发者，直到他们更新之前，数据缺口将持续存在。在此之前，他们的智能体交互和智能体代码行数（例如 agent_edit 的 loc_added_sum 和 loc_deleted_sum）将被低估。这适用于企业、组织和用户报告，以及 1 天和 28 天的报告。
- 我们无法回填缺失的数据。来自受影响 IDE 版本的活动无法标识其来源 IDE，因此事后无法进行归因。随着开发者逐步迁移到这些版本，数据将逐渐恢复，而不是出现单次的大幅跳跃。
- Copilot CLI 指标可能存在虚高，因为部分基于其他 SDK 的客户端活动被计入了 Copilot CLI 活动。随着开发者更新这些客户端，这一问题将得到解决，但早期的 Copilot CLI 指标无法修正，因为这些活动无法与真实的 Copilot CLI 使用区分开来。Copilot CLI 用户无需进行更新。
Why client-side metrics can differ from other Copilot data
为什么客户端指标与其他 Copilot 数据存在差异
Most detailed usage metrics (e.g., feature, language, model, and lines of code breakdowns) come from telemetry that each IDE sends. GitHub also records server-side data when Copilot handles a request. That data reliably shows who was active, but it can’t see what happens in the editor. When your reports and other Copilot data disagree, the gap is usually on the client side:
最详细的 usage 指标（例如功能、语言、模型和代码行数的细分）来自每个 IDE 发送的遥测数据。当 Copilot 处理请求时，GitHub 还会记录服务器端数据。该数据能可靠地显示谁处于活跃状态，但无法看到编辑器内发生的情况。当您的报告与其他 Copilot 数据不一致时，差异通常出现在客户端：
- Telemetry is turned off in the IDE, so no detailed activity is sent.
- A network proxy or firewall blocks the Copilot telemetry endpoint.
- The IDE or Copilot extension is out of date and doesn’t send the events that metrics rely on.
- The client changed how it sends telemetry, as with the Copilot SDK change above.
- The client doesn’t send Copilot telemetry, such as an unsupported or third-party editor.
- IDE 中的遥测功能已关闭，因此未发送详细的活动数据。
- 网络代理或防火墙阻止了 Copilot 遥测端点。
- IDE 或 Copilot 插件版本过旧，未发送指标所依赖的事件。
- 客户端更改了发送遥测数据的方式，如上述 Copilot SDK 的变更所示。
- 客户端未发送 Copilot 遥测数据，例如不受支持或第三方的编辑器。
We’re steadily reducing how much your reports depend on client telemetry. Usage metrics now use server-side data to count active users that client telemetry misses and to identify the IDE for those users, and we’re continuing to expand where server-side data can fill in. Some detail, such as lines of code and accepted suggestions, can only come from the editor, so client-side gaps won’t disappear entirely. The most reliable way to keep your metrics complete is to manage your developers’ environments:
我们正在稳步降低报告对客户端遥测数据的依赖。Usage 指标现在使用服务器端数据来统计客户端遥测遗漏的活跃用户，并识别这些用户使用的 IDE，我们也在继续扩大服务器端数据的补充范围。某些细节（如代码行数和建议接受情况）只能来自编辑器，因此客户端数据的缺口不会完全消失。保持指标完整的最可靠方法是管理开发者的环境：
- Keep IDEs and Copilot extensions current. Use your device management tooling to enforce minimum versions where you can.
- Keep IDE telemetry enabled and allow the Copilot telemetry endpoint through proxies and firewalls.
- Spot outdated clients in your reports. In per-user reports, totals_by_ide includes last_known_ide_version and last_known_plugin_version for each user.
- 保持 IDE 和 Copilot 插件为最新版本。在可行的情况下，使用设备管理工具强制执行最低版本要求。
- 保持 IDE 遥测功能开启，并在代理和防火墙中允许 Copilot 遥测端点通过。
- 在报告中发现过旧的客户端。在按用户生成的报告中，totals_by_ide 包含每个用户的 last_known_ide_version 和 last_known_plugin_version。
To learn how usage metrics combine client-side and server-side telemetry, see Which usage is included? in the Copilot usage metrics documentation.
要了解 usage 指标如何结合客户端和服务器端遥测数据，请参阅 Copilot usage metrics 文档中的“Which usage is included?”。
更进一步：量化金融体系
看懂新闻只是起点——沿量化金融路径，把它变成能交付的工程能力