GitHub's Copilot usage metrics API has been enhanced to provide deeper visibility into how organizations are adopting AI capabilities. Rather than simply counting active users, the updated API now assigns each engaged user to one of four adoption phases, determined by which Copilot surfaces they've interacted with over the past 28 days. A fresh ai_adoption_phase field appears in user-level reports, while a corresponding totals_by_ai_adoption_phase array delivers phase-specific metrics at both enterprise and organization levels.

What's new

The classification system places each engaged user into one of four categories based on their usage of Copilot surfaces across at least two days within the 28-day measurement period:

  • Phase 0 — No cohort: User did not meet the engagement criteria for any phase.
  • Phase 1 — Code first: User engaged with code completion and/or IDE agent mode.
  • Phase 2 — Agent first: User engaged with a single GitHub-based agent surface (i.e., Copilot cloud agent, Copilot code review, or Copilot CLI).
  • Phase 3 — Multi-agent: User engaged with two or more GitHub-based agent surfaces, or with the new GitHub Copilot app.

Each ai_adoption_phase value carries a version field (beginning with v1), allowing the underlying classification logic to adapt as Copilot's feature set expands without disrupting the ability to compare historical data.

Enterprise and organization reports now include the totals_by_ai_adoption_phase array, which organizes engagement and activity data by phase. The metrics encompassed in this grouping are:

  • Total engaged users (2-day-in-28 engagement window)
  • User-initiated interaction average
  • Code generation and acceptance activity averages
  • Lines of code added and deleted averages
  • Pull requests created, merged, and reviewed averages
  • Median time-to-merge average

Aggregated metrics represent the average per user within each phase rather than the sum.

Why this matters

  • Tell the maturity story: Move beyond simple active-user counts and show which Copilot capabilities your developers are actually adopting.
  • Track cohort progression: Watch users graduate from code-first usage into agent-first and multi-agent workflows over time.
  • Target enablement: Focus training, documentation, and rollout programs on the phases where you see the biggest opportunity.

Important notes

  • These metrics are available to enterprise administrators and organization owners who have access to Copilot usage metrics through the REST API.
  • You can use this release in combination with the teams filter ship for greater granularity.