← Back to the wire22 Nov 2026
The AI WireDispatch No. 091
github-changelog ▸ product· filed 7 Nov 2026 · 2 min read

Copilot impact dashboard adds Chat and VS Code Agents usage

GitHub's Copilot impact dashboard now includes Copilot Chat and the VS Code Agents window in its agent adoption chart and 28-day usage metrics reports, and the "Passive users" cohort has been renamed "Chat-first users." The API's `copilot_feature_engagement.totals_by_feature` now returns `chat` and `vscode_agent` entries, though adoption phases and cohort calculations are unchanged. The change is a visibility update: chat-only users are no longer labeled passive, and engagement still requires use on at least two days in the 28-day period.

Machine-drafted illustration · reviewed by a humanFIG. 01

Listen to this dispatch

Narrated by an AI-generated voice.

Copilot impact dashboard adds Chat and VS Code Agents usage

GitHub added Copilot Chat and the VS Code Agents window to the Copilot impact dashboard's agent adoption chart. The chart now covers nine Copilot experiences, up from seven, and the enterprise and organization 28-day usage metrics reports include the same two features.

The "Passive users" cohort was renamed "Chat-first users." GitHub says chat is a core Copilot experience that the dashboard did not previously surface, and labeling primarily-chat users as passive misrepresented how they actually work.

The update follows the feature-level engagement tracking added in September. On the API side, copilot_feature_engagement.totals_by_feature now returns chat and vscode_agent entries for enterprise and organization 28-day reports, matching the chart data.

Adoption phases are unchanged. Chat and the VS Code Agents window count as feature engagement but do not count toward a user's adoption phase. The "Chat-first users" label still maps to the "No Cohort" value in the API, and cohort sizes are unaffected. This is a visibility change, not a change to how adoption is measured.

Engagement follows the same rule as other features: a user is engaged when they have used a feature on at least two days in the 28-day period, and a user can count toward more than one feature. Chat usage captured by metrics includes agent mode, so users who make agent edits are also counted under chat.

Scope is unchanged. Chat and the VS Code Agents window appear only in enterprise and organization 28-day reports, as do the original seven features; reports covering periods before this change include only the original seven. Data access is limited to enterprise owners and billing managers, organization owners, and custom roles with the View Copilot Metrics permission, and the Copilot usage metrics policy must be enabled.

The dashboard now separates active Copilot users who have not reached an adoption phase — the group it calls "Chat-first users" — from users who have. The rename and new chart entries make existing data easier to read; they do not change what gets counted.

Read the original at github.blog →

End of dispatch
More on the wire
99foundry-techcommunity ▸ tooling · filed 19 Nov 2026Deployment Pattern for Foundry Toolboxes with Independent Lifecycles98foundry-devblog ▸ product · filed 10 Nov 2026Microsoft adds agentic mode to Azure Content Understanding for multi-pass document analysis97agent-framework ▸ product · filed 10 Nov 2026Microsoft ships Agent Framework builder skills for coding agents96foundry-techcommunity ▸ product · filed 9 Nov 2026Microsoft Foundry Documents Production Agent Tuning Pipeline Using Agent Optimizer