GitHub says Copilot usage metrics now name customizations
GitHub says Copilot usage metrics now display configured names for organization-created plugins, slash commands, skills, custom agents and Model Context Protocol (MCP) servers on supported clients, rather than generic labels. See the GitHub announcement.
Each customization breakdown now allows up to 25 entries per record, compared with five before. Remaining activity is grouped in a final other entry. Calculations for interaction and distinct-use counts have not changed.
The named breakdowns cover organization and enterprise reporting: one-day aggregate reports, daily totals within 28-day aggregate reports, and per-user reports spanning one or 28 days.
Why it matters
Administrators can use the names to track adoption of internal customizations after rollout and identify where teams may need enablement. Because client telemetry can miss activity, the reports remain a guide to trends rather than a complete usage ledger.
What to keep in mind
AI-generated original factual summary by Reshare AI, based on the linked GitHub Changelog source.
No GitHub review, permission, license or endorsement is claimed. Source content and trademarks remain with their respective owners.
Name reporting covers interactive sessions and prompt mode in Copilot CLI, the GitHub Copilot app, the Copilot SDK, and Agent Client Protocol (ACP) integrations such as JetBrains. For prompt mode, the app and ACP integrations, the minimum Copilot CLI version is 1.0.97. SDK reporting requires version 1.0.21 or newer; IDE agent experiences using that SDK version or newer can also report names. An IDE’s built-in chat telemetry does not report names.
Reports use configured names after trimming whitespace, with a maximum length of 128 characters. Names resembling file paths remain under other or custom. GitHub recommends checking names before sharing reports outside the organization.
Client telemetry can miss usage when clients are outdated or telemetry is blocked. GitHub recommends treating the reports as indicators of adoption and trends, not exact usage accounts.
Only report days processed after the release receive names. Earlier report days keep the generic labels.
The Copilot usage metrics policy must be enabled to access reports. Eligible users are organization owners, enterprise owners, enterprise billing managers, and holders of custom organization or enterprise roles granting the View Copilot Metrics permission.
Claims & sources
GitHub says its Copilot usage metrics now identify organization-created plugins, slash commands, skills, custom agents and MCP servers by configured name, replacing generic categories.
For both organizations and enterprises, named breakdowns appear in one-day aggregate reports, daily totals within 28-day aggregate reports, and per-user reports covering one or 28 days.
Each customization breakdown has increased from a maximum of five entries per record to 25. Remaining activity is collected in a final entry labeled other.
GitHub says the calculation methods remain unchanged for interaction_count and the fields that count distinct uses.
According to GitHub, the named data lets administrators monitor adoption of internal MCP servers, custom agents and skills after rollout and see where enablement may be needed.
Names can be reported through the Copilot SDK, the GitHub Copilot app, Copilot CLI interactive sessions and prompt mode, and ACP integrations. Prompt mode, the app and ACP integrations need a minimum Copilot CLI version of 1.0.97. The SDK minimum is 1.0.21, which also applies to IDE agent experiences using it. Built-in IDE chat telemetry does not report names.
Reported names come from configuration, with whitespace trimmed and a maximum length of 128 characters. Path-like names remain under generic labels. GitHub recommends checking names before reports are shared externally.
GitHub cautions that outdated clients or blocked telemetry can leave usage uncounted. The reports are intended to show adoption and trends rather than provide exact accounting.
Names are available only for report days processed after the release; reports for earlier days retain generic labels.
Access depends on enabling the Copilot usage metrics policy. Reports are available to organization owners, enterprise owners, enterprise billing managers, and users whose custom organization or enterprise roles grant the View Copilot Metrics permission.
Original sources
Swipe up for next1 / 24