趋势解读：Copilot usage metrics API adds cohorts for AI，提升开发者接入体验

To help you tell a deeper Copilot adoption story—not just who is active, but how they’re using Copilot—the Copilot usage metrics API now classifies each engaged user into an AI adoption phase based on their Copilot product usage over a rolling 28-day window. A new ai_adoption_phase field is available on user-level reports, and a new totals_by_ai_adoption_phase array surfaces per-phase metrics on enterprise- and organization-level reports. Each engaged user is assigned to one of four phases based on the Copilot surfaces they’ve used on at least two days in the last 28-day window: 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 includes a version field (starting at v1 ) so the classification logic can evolve as Copilot’s product surface grows, without breaking historical context. On the enterprise- and organization-level reports, the new totals_by_ai_adoption_phase array groups engagement and activity metrics by phase, including: Total engaged users (2-day-in-28 engagement window) Code generation and acceptance activity averages Lines of code added and deleted averages Pull requests created, merged, and reviewed averages