GitHub added REST and GraphQL management for Copilot code-review settings from enterprise to repository scope, explicit attribution and reported MCP or instruction sources for comments. Its impact dashboard and 28-day API reports now also show Copilot Chat and VS Code Agents-window engagement.
Why it matters: Administrators can automate review policy and distinguish Copilot output while measuring two previously hidden usage surfaces. The same update also clarifies that chat and agent-window use do not change adoption phases, preventing an analytics expansion from…
GitHub added repository-level Copilot code-review outcome fields, including addressed comments and merged pull requests without later human change requests. Separate usage fields now flag missing client telemetry and IDE or extension versions below reporting minimums.
Why it matters: Enterprises can distinguish adoption from observable review outcomes and can identify reporting blind spots before using usage data for governance or investment decisions. The new fields still measure actions and telemetry, not code quality or causal impact.
GitHub's Copilot usage API now reports configured names for custom agent components and adds a totals_by_client breakdown for model traffic from OpenCode, Claude Code, Codex, Zed, Copilot CLI, cloud agents, code review and other clients. Reports include requests, sessions, tokens, model and selection mode alongside the optional peer-comparison dashboard.
Why it matters: Administrators can see Copilot consumption outside traditional IDE telemetry and distinguish internal agent components. The same detail can expose sensitive naming or create false precision when client IDs, request counts or opt-in peer groups are treated as…
GitHub added 28-day engagement counts for code completion, agent edit, code review, cloud agents, Copilot CLI and the Copilot app, plus CLI usage fields for skills, custom agents, MCP servers, slash commands and plugins. The fields appear in enterprise and organization reports, with per-user coverage for the CLI customization data.
Why it matters: Administrators can see which agent surfaces and customizations are being used, not just aggregate Copilot activity. The data can guide enablement and cleanup, but connection attempts and invocations are activity signals rather than evidence of successful…