Add VS Code Agents to Copilot usage metrics
GitHub Copilot usage metrics reports now include metrics for activity in the VS Code Agents window, enabling enterprises and organizations to measure adoption and engagement with agents.
GitHub Copilot usage metrics reports now include generally available metrics for activity in the dedicated VS Code Agents window, helping you measure adoption and engagement across enterprises and organizations.
What’s new
Aggregate enterprise and organization reports for both 1-day and 28-day periods now include:
daily_active_vscode_agent_users: An optional count of unique users active in the VS Code Agents window each day.totals_by_vscode_agent: Optional aggregate ofsession_countandtotal_user_messagesvalues.
Enterprise-user and organization-user reports for both 1-day and 28-day periods now include:
used_vscode_agent: An optional indicator of whether the user used the VS Code Agents window.totals_by_vscode_agent: Optional per-usersession_countandtotal_user_messagesvalues.
Why this matters
These metrics help you understand how many people use the VS Code Agents window and how they engage with it. You can use the aggregate reports to track adoption and activity trends, then use the user-level reports to understand usage across teams.
Important notes
- These metrics cover the dedicated VS Code Agents window only. They remain separate from editor-window Agent Mode and generic usage rollups.
- Missing-data behavior is backward compatible — optional fields remain absent or
nullwhen corresponding VS Code Agents-window data is unavailable. - Access is available to enterprise owners and billing managers, organization owners, and anyone with a custom organization or enterprise role granting
View Copilot Metrics. The Copilot usage metrics policy must be enabled.
Visit the Copilot usage metrics API documentation to get started.
The post Add VS Code Agents to Copilot usage metrics appeared first on The GitHub Blog.
Source: original entry ↗
More from GitHub
Follow GitHub to get its new changes in your feed and email digest.
Triage role users can now archive pull requests
Users with triage role or higher permissions in a repository can now archive and unarchive pull requests, expanding access beyond repository administrators to allow more team members to manage inactive pull requests.
Screen readers can navigate timelines as lists
Screen readers can now navigate issue and pull request timelines as a list, with assistive technology announcing list structure, item count, and current position for improved accessibility.
Draft pull requests count toward pull request limits
Draft pull requests now count toward repository pull request limits, giving maintainers better control over managing incoming contributions and reducing low-quality submissions.