GitHub Copilot CLI Metrics Now Available Per-User in Org Reports

TL;DR

• GitHub now shows per-user Copilot CLI activity in organization admin reports
• Admins can track which developers use CLI, session counts, token usage, and CLI versions
• Available now in 1-day and 28-day reports via the REST API

What Dropped

GitHub completed its rollout of Copilot CLI usage metrics by adding per-user breakdowns to organization-level reports. Organization admins can now drill down into individual developer activity on the command line, seeing exactly who's using Copilot CLI and how much.

The Dev Angle

This is the final piece of GitHub's metrics puzzle. After releasing enterprise-level, user-level, and organization-level CLI metrics over the past two months, the per-user org view lets admins answer specific questions: Which developers on my team are actually using Copilot from the terminal? Are we getting adoption across the board, or just a few power users?

The data includes:

• CLI activity flag — whether a user has touched the CLI at all
• Session and request counts — how often they're invoking it
• Token usage — total tokens consumed plus average per request, useful for cost modeling
• CLI version tracking — what version each user is running, critical for planning upgrades and deprecations

All of this is available in both 1-day and 28-day rolling windows, so you can spot trends or sudden changes in usage patterns. The data flows through GitHub's REST API, so it integrates with your existing admin dashboards and reporting tools.

Should You Care?

If you're an organization admin managing Copilot rollout, yes. This solves a real problem: you can now identify which teams or individuals need enablement help, forecast costs more accurately by understanding consumption patterns, and manage CLI version distribution across your org.

If you're a developer using Copilot CLI, this doesn't change your experience — but your admin now has visibility into your usage. If you're on a smaller team or using Copilot sparingly, the impact is minimal. If you're running a large enterprise with hundreds of developers, this data becomes essential for capacity planning and cost allocation.

Access the full dataset via the GitHub REST API documentation.

Source: GitHub Changelog