Copilot Impact Dashboard Adds Chat and Agent Usage

GitHub changed its Copilot impact dashboard on November 6, 2026 to include Copilot Chat and the VS Code Agents window in feature-engagement reporting. The enterprise and organization 28-day reports now cover nine experiences. GitHub also renamed the “Passive users” cohort to “Chat-first users,” addressing a label that understated activity by people mainly using chat.

Engagement means use on at least two days in 28

A user is engaged with a feature when GitHub records use on at least two days during the reporting window. The API adds chat and vscode_agent entries to copilot_feature_engagement.totals_by_feature. A person can be counted under more than one feature.

Chat includes captured Copilot Chat activity, including agent mode, so a user who makes agent edits may appear in both chat and agent-related measures. Counts across categories therefore should not be added as unique people without deduplication.

The renamed cohort does not change adoption-phase logic

Chat-first users remain the No Cohort value in the API. Chat and the VS Code Agents window appear as feature engagement but do not qualify a person for an adoption phase. GitHub says cohort sizes are unchanged by the label change.

Historical periods before the update include only the original seven features, creating a comparability break. A sudden increase after rollout may reflect better coverage rather than changed developer behaviour. Reports should annotate the date and metric definition.

The data requires policy and appropriate roles

The expanded fields are limited to enterprise and organization 28-day reports. Access requires an enterprise owner or billing manager, organization owner or a custom role with View Copilot Metrics, and the usage-metrics policy must be enabled.

Usage data can reveal work patterns. Limit access, define retention and avoid turning activity counts into individual performance rankings. A developer may use an assistant frequently because a task is difficult, not because the tool made the work faster.

Canadian organizations should pair adoption with outcome measures

A responsible evaluation connects feature engagement to reviewed outcomes such as lead time, escaped defects, rework, developer satisfaction and accessibility. Compare similar teams and document other changes instead of attributing every trend to Copilot.

The dashboard improves visibility into use; it does not report causal productivity or code quality. Keep that distinction explicit in procurement, labour discussions and executive reporting.

Sources and editorial method

We use the linked original statements and reports to distinguish documented facts from our analysis. Company announcements describe their authors’ plans and claims; they are not independent verification of future outcomes. This article is dated and will be revised if material evidence changes. Read our editorial standards and corrections process.

GitHub: Copilot impact dashboard adds chat and VS Code agent usage ↗ — Official November 6 changelog; feature definitions, access conditions, cohort rename and comparability limits.