AI 開發工具
GitHub Copilot Usage API No Longer Guarantees Legacy Agent Field; Dashboards Must Switch to Cloud Agent Metric
The compatibility period for `used_copilot_coding_agent` in GitHub Copilot usage reports expired on August 1. Integrations should migrate to `used_copilot_cloud_agent`. The two fields previously returned the same Boolean value, but the legacy field is no longer guaranteed after the deadline, potentially causing enterprise adoption reports to silently undercount usage.
A small but easily overlooked API migration affecting GitHub Copilot usage metrics has reached its deadline. After renaming Copilot coding agent to Copilot cloud agent, GitHub added the `used_copilot_cloud_agent` field to enterprise- and organization-level user reports. The existing `used_copilot_coding_agent` field was guaranteed to remain backward-compatible only through August 1, 2026. According to the official documentation, during the transition period the new and legacy fields returned the same nullable Boolean value for both daily and 28-day rolling windows.
This is not an update to model or agent capabilities, but it directly affects the data pipelines enterprises use to measure agent adoption, license value, and governance coverage. If ETL jobs, SQL models, or BI dashboards still explicitly select the legacy field, they may encounter schema errors. A harder-to-detect scenario is that the data provider retains the field name but stops updating its value, causing agent usage to be understated. Using field presence alone for version detection is also unsafe; integrations should check both value freshness and the null rate.
A more robust migration approach is to treat the new field as primary and the legacy field as a fallback, log differences between them temporarily, and then remove the dependency on the legacy field. Data contracts can add schema validation, daily non-null-rate alerts, and dual-field comparisons during the transition. If a report spans August 1, teams should also verify whether historical data still uses the legacy name to avoid splitting a single time series into two metrics.
The official wording states that the field would “not be deprecated before August 1,” which does not mean it would necessarily be removed on that date. It is therefore not currently possible to assert that the legacy field has been removed from every API response. Engineering teams should rely on responses from the actual endpoints and GitHub’s OpenAPI schema, and treat this event as the end of the compatibility guarantee rather than a confirmed immediate shutdown.