GitHub Copilot CLI Metrics Now Available at the Organization Level
GitHub CopilotGitHub has completed its rollout of GitHub Copilot CLI usage metrics to the organization level, following earlier releases covering enterprise-level (February 27) and user-level (March 5) telemetry. Organization administrators can now view CLI-specific activity data — including daily active CLI users, session and request counts, and token usage totals — within their 1-day and 28-day reports. The addition closes the final gap in CLI metrics coverage across all reporting tiers.
Sources & Mentions
3 external resources covering this update
Organization-Level CLI Metrics Complete the Rollout
GitHub has extended Copilot CLI usage metrics to the organization level, completing a phased rollout that began with enterprise-level reporting on February 27 and user-level reporting on March 5. Organization administrators can now access CLI-specific activity data directly within their existing Copilot usage reports.
This final tier closes the gap in CLI metrics coverage. With all three scopes — enterprise, user, and organization — now reporting CLI activity, the metrics parity between CLI and IDE usage is essentially complete.
What Organization Admins Can Now See
Within their 1-day and 28-day reporting windows, organization administrators have access to three categories of CLI metrics:
- Daily active CLI users — a count of unique users who triggered at least one Copilot CLI interaction per day
- Session and request counts — totals of CLI sessions initiated and requests made within the reporting period
- Token usage — total tokens consumed, along with average tokens per request
These metrics appear alongside existing IDE usage data, giving team leads and platform engineers a unified view of how Copilot is being used across both terminal and editor interfaces.
Why This Matters for Organizations
As GitHub Copilot CLI adoption grows — particularly among developers who prefer terminal-first workflows — the ability to track CLI usage at the organization level fills a practical gap in visibility. Administrators can now compare CLI versus IDE adoption, identify which teams are most actively using the CLI, and use token usage data to forecast consumption costs as access scales.
The rollout mirrors the structure of GitHub's broader Copilot metrics infrastructure, where new reporting dimensions are introduced first at the enterprise level, then extended to user and organization scopes. The completion of this pattern for CLI metrics signals that the feature is now fully production-ready across all supported reporting tiers.