GitHub has expanded its Copilot impact dashboard to include activity from Copilot Chat and the Visual Studio Code Agents window, allowing organisations to monitor engagement across nine Copilot experiences.
The company announced the changes on November 6.
The update also changes the name of an existing user category from Passive users to Chat-first users.
GitHub said the revised terminology better describes developers who use Copilot primarily through conversational features.
Two additional activity categories introduced
The Agent adoption chart now includes Copilot Chat and the VS Code Agents window.
Previously, the dashboard tracked seven Copilot experiences.
The addition increases the total to nine.
The two new categories are also available in enterprise and organisation usage reports covering 28-day periods.
GitHub has added corresponding entries named chat and vscode_agent to the relevant API reporting structure.
Adoption calculations remain unchanged
Although the dashboard now displays more activity, GitHub has not changed the criteria used to calculate adoption phases.
Copilot Chat and the VS Code Agents window are counted as feature engagement.
They do not contribute towards the existing adoption-phase classifications.
The renamed Chat-first users group continues to include people who use Copilot but have not used a qualifying feature on at least two days during the 28-day reporting period.
GitHub said the underlying cohort sizes remain unchanged.
In the API, the group continues to use the value No Cohort.
Activity requires use on two separate days
GitHub defines engagement with a feature as use on at least two days during a 28-day period.
A developer may be counted in more than one feature category.
The Chat category includes activity captured through Copilot Chat usage metrics, including agent mode.
Consequently, developers making agent edits may also appear in Chat engagement reporting.
The dashboard figures should not be interpreted as mutually exclusive counts of individual users across the nine features.
Historical reports retain previous structure
GitHub said reports covering periods before the update will continue to contain the original seven features.
This creates a reporting difference between historical and newly generated data.
Organisations comparing activity across periods will need to account for the change in feature coverage.
The company has not announced that earlier reports will be recalculated to include the new categories.
Access restricted to authorised administrators
The expanded reporting is available to enterprise owners, billing managers and organisation owners.
Users with custom roles granting permission to view Copilot metrics may also access the information.
The organisation’s Copilot usage metrics policy must be enabled.
The November 6 update concerns reporting and classification. It does not introduce a new AI model or change the underlying capabilities of Copilot Chat.
