Evidence note: This article draws on GitHub’s October 6, 2026 announcement. It reports GitHub’s explanation and update advice; independent confirmation and a PlayAgit recovery test are not available.
Reported agent activity fell while usage grew
GitHub reported that Copilot usage metrics could show declining agent activity or agent lines of code while Copilot usage continued growing. The company announced that it had identified the cause and was rolling out a fix. GitHub’s announcement
Why the reporting issue matters
A falling activity chart is insufficient evidence that developers have reduced their use of an agent. Teams evaluating adoption should check whether reporting coverage changed before drawing conclusions from the trend.
The same distinction matters after an update: a rise in recorded activity could reflect restored reporting. It should not automatically be interpreted as increased adoption or improved productivity.
GitHub identified an attribution problem
According to GitHub, some IDEs moved agent sessions to the Copilot SDK without identifying the originating IDE. Most affected activity was omitted from reports; some was attributed to Copilot CLI. GitHub says the issue affects IDE versions using the SDK for agent mode. GitHub’s explanation
The fix requires IDE updates
GitHub advises updating affected IDEs. Its October 6 announcement lists Visual Studio Code 1.139.0 and later as fixed, with other IDE releases expected through November 2026. Those dates describe GitHub’s rollout expectations, not verified completion. GitHub’s update guidance
Developer takeaway: update, then assess recovery
Teams should inventory IDE versions, follow the linked update guidance, and record update dates alongside subsequent metric reviews.
GitHub says missing historical activity cannot be recovered and expects reporting to recover gradually as developers update. It gives no exact date for an individual organization’s recovery. GitHub’s reporting expectations
The useful follow-up question is whether reporting resumes for developers on fixed versions. Answering it requires post-update observations; the announcement alone does not establish that outcome.