Developer tools · Source-backed update

Copilot in JetBrains Air: billing and usage limits

Air tasks use Copilot plans, with separate controls and reporting limits. GitHub also adds BYOK breakdowns to its usage metrics API.

Published GitHub · Announcements 3 NovemberEdited by Clinton Feyisitan

Review scope: two GitHub announcements and API documentation read 4 November 2026. No Air task, paid execution or authenticated reporting tested; no quality winner or new price inferred.

Which subscription pays for Air tasks?

GitHub’s 3 November announcement brings Copilot to JetBrains Air through the Agent Client Protocol. Local tasks connect through the Air plugin. Cloud tasks require an Air Teams-enabled business organization, an existing Copilot subscription and administrator enablement.

Cloud tasks consume the Copilot plan rather than JetBrains AI credits. A task cannot select between a personal and organization Copilot plan. Air may discover missing subscription access or credits only when the cloud environment starts.

Air’s analytics do not include Copilot usage, and its administrators cannot set Copilot spending limits inside Air. They can disable the integration. These boundaries matter when reconciling a team’s usage; connecting an account is not proof that every task will run.

Read GitHub’s Air announcement. The Copilot profile keeps subscription prices separately dated.

BYOK reporting separates usage, not invoices

A separate 3 November update adds local bring-your-own-key and enterprise custom-model breakdowns to Copilot usage reports. Local requests go directly to a developer’s provider or local model; enterprise custom requests route through GitHub.

The new breakdowns are already part of existing totals: adding them again would double-count usage. Local fields can undercount when telemetry is disabled or a provider does not return token usage. Enterprise custom-model counts are observed server-side; the new custom-model marker is not backfilled into older reports.

These metrics help distinguish where requests run. They do not establish provider charges, complete local usage or savings. GitHub documents the fields and limits.

Check the reporting period and scope

The usage metrics API documentation describes authorized enterprise access, daily reports and the latest complete available 28-day reporting window. Reporting requires the relevant metrics policy and permissions. A partial current day should not be compared with a complete period.

Use the stack cost calculator for separately entered bills, and the Copilot profile for separately dated plan context. Neither converts usage counts into an invoice automatically.

Source receipts and limitations.