GitHub Copilot impact dashboard adds Chat and VS Code agent usage
GitHub's Copilot impact dashboard now shows Copilot Chat and VS Code Agents window engagement, giving a fuller view of developer usage.
GitHub has expanded the Copilot impact dashboard to report engagement with Copilot Chat and the VS Code Agents window, according to a release note published November 6, 2026. The Agent adoption chart now covers nine Copilot features in total, up from the original seven, so admins can see how users engage with chat alongside the other tools.
The update also renames the “Passive users” adoption cohort to “Chat-first users.” GitHub says the new name better describes who is in the group: people who are active in Copilot but haven’t used a qualifying feature on at least two days in the 28-day period. Cohort sizes don’t change, and the cohort remains the No Cohort value in the API.
Enterprise and organization 28-day usage metrics reports now include chat and vscode_agent entries under copilot_feature_engagement.totals_by_feature. Chat covers Copilot Chat use captured by usage metrics, including agent mode, so a user who makes agent edits is counted under chat as well as other features. Reports for periods before the change include only the original seven features.
Adoption phases are unchanged. Chat and the VS Code Agents window are reported as feature engagement but don’t count toward adoption phases.
Why it matters
Chat is a core Copilot experience, but the dashboard previously left it out, and users who relied mainly on chat were labeled passive. The change gives a fuller picture of how developers use Copilot and renames the cohort so its label matches the behavior it describes.
What to do
Enterprise owners, billing managers, organization owners, and users with a custom role that grants the View Copilot Metrics permission can review the new data now. Teams comparing adoption over time should account for the change, since reports from before it include only seven features. Confirm current details on GitHub’s changelog or documentation before updating internal reporting.
The Stack Brief
Get the weekly brief
One email a week: SaaS pricing changes, launches worth knowing about, and one comparison you can act on.

Comments
Join the discussion with your GitHub account. Be civil, stay on topic.