Tools2 min read

GitHub changes its Copilot report: Chat-first does not mean higher productivity

Copilot reporting now includes Chat and VS Code Agents. What business owners should check before comparing their team’s figures across the change.

Prepared by the NADALI editorial team using AI

Conceptual AI illustration: blue and amber cards with abstract charts beside a checklist and ruler.
Надалі / Nadali — концептуальна ілюстрація, створена за допомогою OpenAI / conceptual illustration generated using OpenAI. · Original AI-generated editorial illustration created for Nadali; no third-party reference assets. Use subject to applicable service terms and law; no exclusive copyright guarantee. · 1440 × 960

Author: Nadali. Prepared using AI.

On November 6, 2026, GitHub announced an update to Copilot impact reporting: it now includes Chat and the VS Code Agents window. Passive users was renamed Chat-first users; cohort sizes and rules for moving between adoption phases have not changed.

Who should care

Small-business owners with an in-house development team, or people responsible for its budget. Before renewing licenses, check whether work outcomes have changed or only their presentation.

This is a reporting change, not evidence that developers are working faster.

Comparing periods

GitHub says the additions apply to organization and enterprise 28-day reports. Older periods do not gain the new categories. Chat and VS Code Agents usage does not itself count toward adoption phases. People can appear under multiple features, so their sum should not be treated as a unique-person count.

Access and limitations

GitHub’s documentation requires the Copilot usage metrics policy to be enabled. Access is available to organization and enterprise owners, enterprise billing managers, and users with the relevant custom metrics-viewing permission. This is not a personal report automatically available to every employee.

GitHub also cautions that the dashboard’s potential return-on-investment estimates are directional, not exact financial results.

What an owner should do

Our editorial recommendations:

  1. Ask the report owner to record the reporting period, scope and metric definitions.
  2. Annotate the change beside the chart. Do not join different sets of categories into an apparently continuous trend.
  3. Separately review accepted work, checking time and error correction. Tool-use frequency does not replace those measures.
  4. Support budget decisions with your own comparison of costs and outcomes. Our guide to measuring time savings offers a starting point.

Takeaway: the updated dashboard makes more ways of using Copilot visible. Judging business value still requires separate evidence about the team’s work.

Primary sources checked November 8, 2026. Nadali has not tested the dashboard in an account or measured a team’s productivity. The cover is a conceptual AI illustration, not a GitHub screenshot. 

Sources and verification

  1. Copilot impact dashboard adds chat and VS Code agent usage ↗
    Source checked: 2026-11-08
  2. Viewing the Copilot impact dashboard ↗
    Source checked: 2026-11-08