Your customizations.
Now visible by name.
See which skills, agents and MCP servers your developers use. Copilot usage metrics now report configured names instead of grouping your customizations under other or custom.
What changed in the report
- Configured names
- Skills, custom agents, MCP servers, slash commands and plugins, identified in their
totals_by_*lists. - 5 → 25 entries
- Up to 25 named entries per list, with remaining activity in a trailing
otherentry. - Same counts
interaction_countanddistinct_*_use_countare calculated as before.
One day. Two report formats.
Pick a day and a category. Both columns use that day's activity: September format on the left, October format on the right. The date changes the activity, not the formats.
Grouped under
Configured names, up to 25 + trailing other
Organization activity · organization-28-day
Daily interactions: named vs grouped
Reported by nameGrouped (
other / custom)Leaderboard since names appeared
Track adoption after a rollout
Pick one of your customizations. Bars come from the aggregate reports; the line counts developers from the per-user reports.
Daily usage
interaction_count (reported)Hidden inside other (simulated truth)Developers using itWhere to focus enablement
Team = developers active since Oct 22 who used it at least once. Team membership is what you would join from the user-teams-1-day report.
Per-user report · users-1-day
Raw record
Simulated API explorer
Endpoints return signed download links; the report itself is an NDJSON file. Both steps are simulated here.
Request download links
Download the report file
How a configured name is reported
Names are trimmed and limited to 128 characters. Names that look like file paths stay grouped. (Path detection here is an approximation for the demo.)
Reported as
Analyze a report file
Drop a real NDJSON report from the API (aggregate 1-day, 28-day, or per-user) or load a simulated one. Files are parsed locally in your browser and never uploaded.
How to get a real report file
From a local clone of this repository, run the following in PowerShell. You need Node.js 20+ and GitHub CLI (gh) signed in to an account with Copilot metrics access.
$env:GITHUB_TOKEN = gh auth token node .\scripts\summarize.mjs --org YOUR_ORG --report organization-28-day --save .\copilot-report.ndjson
Replace YOUR_ORG with your organization's login, not your personal username. The organization's usage metrics policy must be enabled, and your token needs appropriate permissions (read:org for classic tokens). Organization owners and roles with View Copilot Metrics can access these reports.
This saves copilot-report.ndjson in the current folder. Click Choose a file above and select it. The script requests signed download links, downloads every report part, and saves the actual NDJSON. Do not upload the JSON response containing download_links.
For developer reach in the full insights dashboard, also download the matching per-user report and load both files together:
node .\scripts\summarize.mjs --org YOUR_ORG --report users-28-day --save .\copilot-users.ndjson
The aggregate 28-day report contains daily history. The per-user 28-day report contains period totals, not daily user history; reach is available only for its full reporting window. To analyze user reach over individual days, download users-1-day reports with --day YYYY-MM-DD. For enterprise reports, replace --org YOUR_ORG --report organization-28-day with --enterprise YOUR_ENTERPRISE --report enterprise-28-day and use a token with enterprise metrics access.
Need trends or developer reach? Load matching files in the dashboard → Files are not transferred between pages.
Good to know
Coverage
Names come from Copilot CLI (interactive and prompt mode), the GitHub Copilot app, ACP integrations such as JetBrains, and the Copilot SDK. Prompt mode, the app and ACP need CLI 1.0.97+; the SDK needs v1.0.21+. IDE built-in chat telemetry does not report names.
History
Names appear for report days processed after the release. Earlier days still show other or custom, as in the dashboard above.
Accuracy
Metrics come from client telemetry and can undercount (outdated clients, blocked telemetry). Use them for trends and adoption, not exact accounting.
Review before sharing
Names are reported as configured. Review them before sharing reports outside your organization.
Access
Enterprise owners, billing managers, organization owners, or a custom role with “View Copilot Metrics”. The Copilot usage metrics policy must be enabled.
Plugins ⊂ skills
Plugin totals count only plugin skill invocations, so they are already included in skill totals. Don't add the two together.
Try it on your real data
Follow the real-report download instructions, then open your files in the insights dashboard for trends, named activity, developer reach, and actionable insights.
See the README and the Copilot usage metrics API docs.