GitHub Copilot Usage Metrics: CLI Activity Now Tracked at Enterprise Level
GitHub CopilotGitHub has expanded its enterprise-level Copilot usage metrics to include telemetry data from the Copilot CLI, giving enterprise administrators visibility into terminal usage alongside existing IDE and web metrics. The new CLI metrics cover daily active CLI users, session and request counts, and token consumption totals including per-request averages. This addition completes the cross-environment picture for enterprises looking to measure Copilot adoption comprehensively across all development surfaces.
Sources & Mentions
3 external resources covering this update
GitHub Copilot Usage Metrics: CLI Activity Now Tracked at Enterprise Level
GitHub has expanded its enterprise-level Copilot usage metrics to include telemetry data from the Copilot CLI.
New CLI Metrics
The following metrics are now available at the enterprise level for Copilot CLI:
- Daily Active CLI Users: Count of unique users who interacted with Copilot through the CLI on a given day.
- Request and Session Counts: Total number of CLI requests and sessions, providing granularity into how frequently the CLI is used.
- Token Usage: Total tokens consumed by CLI interactions, including per-request averages for cost estimation and budget planning.
Enterprise Use Cases
These metrics enable several enterprise workflows:
- Cross-surface Comparison: Compare CLI adoption against IDE and web usage to understand where developers are most active with Copilot.
- Budget Forecasting: Use token consumption data to project costs and allocate budgets across teams.
- Enablement Tracking: Measure the effectiveness of CLI rollout and training programs by tracking adoption curves.
Access Method
CLI activity data is accessible through the existing enterprise-level Copilot usage metrics API and dashboards, requiring no additional configuration beyond enabling CLI telemetry collection.