GitHub Copilot

The GitHub Copilot connector imports Copilot usage and billing from GitHub.

GitHub Copilot is seat-based: you pay a fixed monthly subscription per user plus variable consumption for premium requests (agent runs, extended thinking and so on). Cloud Ctrl pulls two feeds:

  • The billing report — what you were actually charged, broken down by seat and premium-request lines. Dashboard spend comes from this.
  • The premium-request usage report — which models each user consumed. The per-model and per-user breakdown comes from this.

The fixed monthly seat subscription is split across the people who hold a seat, weighted by their premium-request consumption — so heavier users carry more of the subscription cost and someone who barely used Copilot pays next to nothing. Shares for a month always add back up to exactly what GitHub billed, so your total spend matches your GitHub invoice.

Get an access token

The connector authenticates with a GitHub access token (a personal access token or app installation token) with these scopes:

  • manage_billing:copilot
  • read:org

You need to be an organization owner or billing manager.

One-click token creation

Open the pre-scoped token page — Create a GitHub token (scopes pre-filled) — which creates a token with both scopes already ticked.

Warning

The token belongs to a user, so prefer a service account over an individual's account so the connection survives staff changes.

See also GitHub's Copilot billing docs.

Add a Credential

  1. Open Settings → Cloud Connections → GitHub Copilot
  2. Click + Add Credential
  3. Enter a display name and paste the access token
  4. Click Submit

Add a Cloud Account

  1. From Settings → Cloud Connections → GitHub Copilot, click + Add Cloud Account
  2. Select the credential you just added
  3. Choose the billing scope:
    • Organization (default) — enter the GitHub organization login (slug). Use this when the organization is billed for Copilot directly.
    • Enterprise — enter the GitHub enterprise login (slug). Use this when the organization's Copilot is administered by a GitHub enterprise account; the organization endpoints return 404 in that case.
  4. Click Submit

Attribution notes

  • Premium-request spend by model and user — Cloud Ctrl breaks premium-request spend down by model and distributes it across users by their consumption share. When no per-user signal is available (usage-metrics policy disabled or the token lacks the scope), seat cost falls back to an even split across seat-holders, so cost still lands on people rather than left unallocated.
  • Allowance vs on-demand — each seat includes an allowance of premium requests. Requests inside the allowance show their usage with a net cost of $0 (which is what GitHub charges); requests beyond it add to your spend. A user working entirely inside their allowance costs $0 but may be one of the heaviest consumers on the team.
  • Repository attribution — the billing report can include the repository a request was made in, when GitHub exposes it. This depends on your enterprise settings, so it may show as unattributed.
  • Cost centres — GitHub Copilot supports native cost centres; when the cost-centre report is available, Cloud Ctrl maps each user and organisation to its cost centre. Use Tag Mapping to map cost-centre names or user logins to additional dimensions.
  • Reconciliation — if the aggregate and per-model reports don't match exactly (e.g. one lags the other), Cloud Ctrl emits a residual row for the difference so totals always reconcile to the authoritative billing total. No spend is silently dropped.
  • History — GitHub exposes Copilot billing for the current billing cycle, so there is no deep historical backfill for this connector.