GitHub Copilot usage
metrics, per engineer.

How to check your own Copilot usage

Copilot counts usage in AI credits. Where you see yours depends on the plan:

• On a Copilot Business or Enterprise seat: click your profile picture, then Copilot settings. Under Usage, Usage this cycle shows the credits you've used.
• On a personal plan: github.com/settings/billing, then AI usage, with the credits each model used and their cost.
• In the Copilot CLI, /usage shows this session's tokens per model and, on token-based billing, each model's AI credits.

The Copilot usage metrics dashboard

Enterprise owners open the enterprise, then Insights, then Copilot usage; organization owners get the same view for their organization. Billing managers and custom roles with the View Copilot Metrics permission can see it too, once the Copilot usage metrics policy is on. It shows 28-day trends in three dashboards:

• Copilot usage: daily and weekly active users, code completions and their acceptance rate, requests per chat mode (ask, edit, plan, agent), and model and language use. Copilot CLI isn't in these charts.
• Code generation: lines changed with AI, and the share that agents added or deleted.
• Copilot impact: users grouped into adoption phases, compared on pull requests merged per user per month and time to merge.

The Copilot usage metrics API

The REST API returns the same data as files. Each endpoint under /orgs/{org}/copilot/metrics/reports/ (or /enterprises/{enterprise}/…) answers with signed links to NDJSON reports: one day or the latest 28 days, for the organization, per user, per repository, or per user and team. An organization token needs read:org, or the Organization Copilot metrics read permission. Data can lag up to three full UTC days and goes back up to a year.

Each per-user line has user_login and day, prompts sent, code generated and accepted, lines added and deleted, flags such as used_agent, used_chat and used_cli, ai_credits_used, and totals by IDE, feature, language and model. It has no pull requests. The old /orgs/{org}/copilot/metrics endpoint closed on April 2, 2026.

curl -L \
  -H "Accept: application/vnd.github+json" \
  -H "Authorization: Bearer <YOUR-TOKEN>" \
  -H "X-GitHub-Api-Version: 2026-03-10" \
  "https://api.github.com/orgs/ORG/copilot/metrics/reports/users-1-day?day=DAY"

How Zest measures GitHub Copilot usage

GitHub's reports describe Copilot. Claude Code, Cursor or Codex sessions on the same engineer's laptop aren't in them, which is why Claude Code vs GitHub Copilot, Codex vs GitHub Copilot and Cursor vs GitHub Copilot are worth measuring on your own team. Zest answers the cross-tool question: which coding agent, model and skills each engineer reaches for, and which sessions turn into merged pull requests.

• The Zest extension for VS Code (setup) reads Copilot Chat sessions: the conversation, the models, the tokens Copilot reports, and the skills and tools each one called.
• Inline completions are not captured. GitHub's own metrics stay the source for completion acceptance.
• Claude Code, Codex, Cursor, Grok Build and Hermes report into the same dashboard, so usage is comparable across tools.

Copilot ROI: usage next to what ships

GitHub's impact dashboard compares adoption phases on merged pull requests. Zest shows it per engineer: the Zest GitHub App puts each engineer's Copilot Chat sessions next to the pull requests they merged, with PR cycle time. Which delivery numbers to trust is on developer productivity metrics.