What changed
GitHub made dedicated VS Code Agents-window metrics generally available in one-day and 28-day Copilot reports. Aggregate and user-level fields now expose active users, session counts and message counts separately from editor Agent Mode and generic Copilot rollups.
Why it matters
Administrators can distinguish adoption of the dedicated agent surface from other Copilot use, but activity counts still do not establish code quality, productivity or business value.
What to do
Enable the metrics policy for a consenting pilot, segment the dedicated Agents window from Agent Mode, compare sessions with reviewed task outcomes and costs, and restrict user-level reports to an approved governance purpose.
Caveat
This is usage telemetry, not outcome measurement. Optional fields can be absent or null, access is role-gated, and GitHub supplies no independent evidence that more sessions or messages improve software delivery.