GitHub announced on November 3, 2026 that eligible software teams can run Copilot coding tasks on remote computers through JetBrains Air using their Copilot subscription.
Air is a workspace for directing coding agents and reviewing their work. Copilot already appeared in JetBrains’ October Air announcement; the new development is the Copilot-funded cloud option.
Who can use it
GitHub lists three requirements: a JetBrains account in a business organization with Air Teams enabled, a Copilot subscription and an Air administrator’s permission to use Copilot. Tasks can start in a browser or a JetBrains coding environment. The announcement does not enumerate eligible Copilot tiers.
Repository access needs separate setup. For projects owned by a GitHub organization, JetBrains’ setup guide requires administrators to grant the Air connection app access to the relevant repositories.
Where to control the bill
GitHub says these tasks use Copilot allowances rather than JetBrains AI credits. However, JetBrains’ general credits guide still says cloud tasks consume JetBrains credits. The documents conflict, and the announcement does not establish all-in Air Teams or cloud infrastructure costs.
GitHub also says Air excludes this Copilot usage from analytics and cannot set Copilot spending limits. Administrators can disable access, but users cannot choose personal or organization billing per task. Which plan takes precedence is not explained.
For usage billed to a Copilot Business or Enterprise organization, GitHub’s billing rules provide a shared monthly credit allowance. Paid usage beyond that pool is enabled by default unless an administrator disables it. Cost depends on the model and tokens—the units of content processed and generated. Reusing a subscription does not mean unlimited tasks.
GitHub’s budget controls address two different goals:
Limit individual consumption: user-level budgets count usage from the included pool and always stop further credit-consuming usage at the limit.
Limit additional charges: organization, cost-center and enterprise spending budgets require “Stop usage when budget limit is reached” to be enabled. It is off by default; otherwise, charges can continue past the budget.
Organization owners can set organization-level budgets; enterprise owners and billing managers can configure the broader controls. These organizational rules should not be assumed to apply to personal Copilot plans.
The practical implication is to separate permission to run tasks from permission to spend. Before enabling cloud access, establish which account will pay and who can enforce its budget. Capping extra charges alone does not limit one person’s use of a shared allowance.
Teams considering unattended services face a separate access decision, covered in our guide to organization-owned Copilot agents.