GitHub Copilot Metrics: Plan Mode Telemetry Now Tracked
GitHub has expanded Copilot usage metrics to include dedicated tracking for plan mode activity. Previously, plan mode usage was grouped under the generic "Custom" category in the metrics dashboard and API; it now appears as a distinct chat_panel_plan_mode dimension. Enterprise and organization administrators can view plan mode breakdowns in the Copilot usage dashboard under Insights, with support available across JetBrains, Eclipse, Xcode, and VS Code Insiders — and general VS Code support expected shortly.
Plan Mode Telemetry Added to Copilot Usage Metrics
GitHub has updated its Copilot usage metrics to properly track plan mode as its own dedicated category. This change gives enterprises and organizations clearer visibility into how developers are using plan mode — a feature that allows developers to create and refine step-by-step implementation plans directly in their IDE before committing to code.
What Changed
Until this update, plan mode interactions were bucketed alongside other activity under the "Custom" label in both the metrics dashboard and the API. That grouping made it difficult for administrators to understand actual plan mode adoption separately from other custom Copilot usage patterns.
With this change, plan mode activity is now reported under the key chat_panel_plan_mode within three API dimensions:
totals_by_featuretotals_by_language_featuretotals_by_model_feature
In the dashboard UI, plan mode breakdowns are accessible under Insights > Copilot usage, where administrators can view request counts and model usage attributed specifically to plan mode interactions.
IDE Support
Plan mode telemetry is currently supported for the following environments at the enterprise, organization, and user levels:
- JetBrains IDEs
- Eclipse
- Xcode
- VS Code Insiders
Support for the generally available VS Code release is forthcoming and expected in a future update.
Impact on Existing Metrics
Administrators who track Copilot usage trends should be aware that this reclassification may cause an apparent dip in "Custom" usage figures in their historical charts. This is expected — the activity that was previously counted as "Custom" is now correctly categorized as plan mode. No actual usage decline has occurred; the data has simply been re-attributed to the proper dimension.
To access this feature, plan mode metrics must be enabled via AI Controls > Copilot > Metrics > Copilot usage metrics at the enterprise or organization level, and the "Copilot usage metrics" feature must be enabled at the relevant level.