GitHub fixes Copilot agent metrics gap; missing activity cannot be backfilled
GitHub said on October 6 that some Copilot agent activity had been missing from usage metrics after several IDEs moved agent sessions to the Copilot SDK. Those sessions did not identify their originating IDE, preventing correct attribution. Most affected activity was omitted; some was counted as Copilot CLI activity.
The issue applies to IDE versions that use the Copilot SDK for agent mode, not every Copilot client. GitHub said the fix was available in Visual Studio Code 1.139.0 and later. Its October 6 notice expected fixes for other IDEs through November; that forecast does not establish that every listed IDE has shipped its fix today.
GitHub says billing was not affected. The bug changed attribution in usage metrics, not charges. Agent interactions and agent lines of code remain undercounted for developers on affected versions until they update, including enterprise, organization and user reports over both one-day and 28-day periods.
Missing activity cannot be backfilled because the affected events do not identify their IDE. GitHub says reports should recover gradually as developers update. Earlier inflated Copilot CLI metrics also cannot be corrected because misattributed events cannot be separated from genuine CLI use. Copilot CLI users do not need to update for this issue.
Detailed feature, language, model and lines-of-code metrics depend on editor telemetry. Disabled telemetry, blocked endpoints, outdated extensions and unsupported clients can create other gaps. GitHub uses server-side data to improve active-user counts, but says some details, including lines of code and accepted suggestions, still require editor events.
For teams evaluating adoption, a drop in reported agent activity is not by itself evidence that developers stopped using agents. Review client versions and telemetry coverage before comparing periods or drawing productivity conclusions. GitHub points administrators to last-known IDE and plugin versions in per-user reports; this notice does not promise retrospective recovery.