Previous CLI metrics releases added a standalone totals_by_cli section to the Copilot usage metrics API with session counts, request counts, and token usage. That section reported CLI activity separately from the rest of the report—top-level totals and dimensional breakdowns reflected IDE activity only.

With this update, CLI activity is now integrated into the metrics you already use.

What’s new

Top-level totals now include CLI contributions. The following fields now represent IDE + CLI combined:

  • code_generation_activity_count
  • code_acceptance_activity_count
  • user_initiated_interaction_count
  • loc_added_sum / loc_deleted_sum

CLI appears in dimensional breakdowns as feature=copilot_cli in:

  • totals_by_feature
  • totals_by_model_feature
  • totals_by_language_feature
  • totals_by_language_model

CLI is excluded from totals_by_ide. The existing totals_by_cli section and per-user CLI fields added in recent releases remain unchanged.

This impacts our single-day and 28-day enterprise, organization, and per-user reports.

Why this matters

  • Unified view of Copilot usage. Top-level totals now reflect all Copilot activity across surfaces, so dashboards and reports no longer undercount usage for organizations with CLI adoption.
  • Compare CLI alongside other features. CLI activity appears in the same totals_by_feature breakdowns as code completions, letting admins see how usage distributes across Copilot capabilities.
  • No more manual stitching. Previously, building a holistic view of Copilot output required combining totals_by_cli with IDE-only totals. That’s now handled by the API itself.

Important notes

  • Top-level totals have changed meaning. If your dashboards or reporting assumed these fields represented IDE-only activity, the numbers will increase to reflect the addition of CLI contributions. Review any thresholds or comparisons that depend on these values.

Visit our API documentation to learn more. Join the discussion within GitHub Community.