GitHub has corrected the way Copilot agent sessions are reported by updating the Copilot SDK handling in affected IDEs. The change restores proper attribution of agent activity and lines of code, which is essential for accurate usage dashboards, capacity planning, and downstream automation that relies on these metrics.
Root Cause and Fix
Several IDEs recently migrated Copilot agent sessions to the Copilot SDK. In the SDK‑based mode the client no longer identified the originating IDE, so the usage service could not attribute the activity. The result was a systematic under‑count of agent activity and agent lines of code in the Copilot usage metrics, while overall Copilot usage appeared to grow.
The fix consists of a version bump that restores the IDE identifier in SDK calls. Visual Studio Code version 1.139.0 and later already include the fix. Upcoming releases for Visual Studio 18.12, JetBrains, Eclipse, and Xcode are scheduled through November 2026. Once a developer upgrades to a fixed version, their agent interactions are recorded again in the dashboard and API.
Operational Impact
Because the missing data cannot be back‑filled, any reporting period that includes developers on an affected IDE version will show a permanent gap for those users. Billing is unchanged; the discrepancy only affects the granularity of the usage reports. In the interim, the Copilot CLI metrics may appear inflated because activity from SDK‑based clients was mistakenly counted as CLI usage. This inflation will resolve as developers update, but historic CLI numbers cannot be retroactively corrected.
Practitioners who rely on per‑user or organization‑level reports should be aware that the totals_by_ide field now includes last_known_ide_version and last_known_plugin_version, which can be used to spot outdated clients.
Implementation Recommendations
- Enforce minimum IDE versions: Use device‑management or configuration‑management tools to push the fixed IDE releases to all developers.
- Keep telemetry enabled: The agent metrics depend on client‑side telemetry. Ensure that IDE telemetry settings remain on and that the Copilot telemetry endpoint is allowed through any network proxies or firewalls.
- Monitor reports for gaps: Regularly review the
totals_by_idesection of per‑user reports to identify developers still on pre‑fix versions. - Validate CLI data: When analyzing CLI usage trends, factor in the temporary inflation caused by mis‑attributed SDK activity.
Related CloudNinjas coverage: AI engineering.
What This Means For Practitioners
Update all affected IDEs as soon as the fixed version is available; otherwise agent activity will remain invisible in metrics and may lead to inaccurate capacity or adoption decisions. Incorporate version checks into your CI/CD or device‑policy pipelines to guarantee compliance. Verify that network policies permit the Copilot telemetry endpoint, and keep telemetry enabled to avoid future blind spots. Finally, treat the current CLI metric spike as an artifact of the bug and adjust any alerts or thresholds accordingly.
