GitHub Copilot in JetBrains Air: Setup and Cloud Limits
Learn how Copilot works in JetBrains Air locally and in Air Teams, including setup, cloud requirements, plan credits, isolation and limitations.
GitHub announced on November 3, 2026 that GitHub Copilot can be selected directly in JetBrains Air for coding-agent tasks. The integration uses Agent Client Protocol (ACP) and supports work in local JetBrains IDE sessions as well as remote tasks through Air Teams. It is particularly useful for developers who already pay for Copilot and want to delegate, inspect, and iterate on work without switching to a separate agent subscription.
The important distinction is that the local and cloud experiences do not have identical requirements. A developer can select Copilot locally with an existing subscription; remote tasks require an organization using Air Teams, an enabled Copilot integration, and a connected repository. This is a new Air workflow announcement, not the first time Copilot has worked in JetBrains IDEs.
How to start Copilot in JetBrains Air
- For local work, install Air in a supported JetBrains IDE, choose GitHub Copilot from the agent picker, and connect the GitHub account with the Copilot subscription.
- For cloud work, confirm that your organization has Air Teams enabled, the administrator permits Copilot, and the relevant Git repository is connected.
- From the browser, open Air, connect GitHub in Settings > VCS Providers, choose the repository and remote branch, select Copilot, and submit a task.
- Alternatively, in the JetBrains IDE Air plugin, choose Cloud as the execution environment, select Copilot, and start the task.
- Review the resulting changes and tests before merging; do not assume an agent's output is production-ready.
Local versus cloud: the practical differences
Choose the right execution environment
| Question | Local Copilot in Air | Copilot through Air Teams |
|---|---|---|
| Where it runs | Local IDE workflow | Isolated remote container on a fresh virtual machine |
| What you need | Air integration and an eligible Copilot subscription | Air Teams business organization, Copilot subscription, admin enablement and repository access |
| How to launch | Agent picker in IDE | Browser or IDE with Cloud selected |
| Environment | Uses local project context and tools | Remote checkout and configured environment; does not automatically inherit your laptop setup |
| Review | Inspect local changes | Review remote task results and branch changes |
GitHub says Copilot cloud tasks through Air use the Copilot plan rather than JetBrains AI credits. That is a product-specific exception worth checking: JetBrains' general Air cloud-task documentation describes the default JetBrains-provider billing model, while GitHub's November 3 integration announcement explicitly describes Copilot-subscription billing for Copilot tasks. Neither source supplies a universal per-task dollar price. Check your current subscription allowance and organizational policies before estimating costs.
Cloud isolation and team governance
For the Copilot integration, GitHub describes a fresh virtual machine with a Docker container, proxied traffic, and no state carried from one task to the next. The remote agent can install dependencies, build, and test without changing the developer's local machine. JetBrains' Air Teams documentation also makes clear that repositories and environment settings must be configured for remote work: do not assume local secrets, installed tools, or working-tree changes are automatically present in the cloud.
Air administrators can disable Copilot as an available agent, but GitHub says they cannot set Copilot spending limits inside Air itself. The Air governance and analytics dashboard also does not report Copilot usage. Teams should therefore monitor their GitHub Copilot subscription and billing outside Air rather than treating Air's JetBrains AI credit dashboard as a complete cost report.
What can fail or surprise you
- Air can defer subscription or credit validation until a cloud environment starts, so a connected account does not guarantee the task will launch.
- You cannot select whether a particular Copilot cloud task uses a personal versus organization Copilot plan.
- Copilot cloud usage is not included in Air's own governance and analytics metrics.
- The Copilot integration does not automatically make every existing JetBrains AI Assistant workflow an Air Teams cloud task.
- Cloud tasks still need code review, testing, and appropriate repository permissions.
For a realistic first test, choose a small repository task with a clear acceptance criterion, such as updating a failing unit test. Compare how much setup is needed locally and remotely, verify the generated branch diff, and record which Copilot subscription was charged. This gives a more useful evaluation than assuming cloud execution is automatically cheaper, faster, or safer for every project.
Questions people ask
How do I enable GitHub Copilot in JetBrains Air?
For local work, install Air in your JetBrains IDE, select GitHub Copilot in the agent picker, and connect the GitHub account that has your Copilot subscription. For remote work, your organization must have Air Teams, repository access, and administrator permission for Copilot. In the browser, connect GitHub under Settings > VCS Providers before launching a cloud task.
Do Copilot cloud tasks in Air use JetBrains AI credits?
GitHub's November 3, 2026 announcement says Copilot tasks launched through Air Teams use your GitHub Copilot plan, not JetBrains AI credits. This is specific to the Copilot integration; JetBrains' general cloud-task documentation describes different default billing for other agents. The sources do not give a universal per-task price, so verify your Copilot allowance and organization billing before running many tasks.
Can I use Copilot in Air Teams with a personal account?
Local Copilot use in Air can work with an eligible Copilot subscription. Cloud tasks require membership in an Air Teams-enabled business organization, an administrator who allows Copilot, and access to the target repository. GitHub also warns that users cannot manually choose whether an individual cloud task draws on their personal or organization Copilot plan. Check the organization's setup before assuming personal access alone is sufficient.
Does a Copilot cloud task change files on my laptop?
No. GitHub describes Copilot cloud tasks in JetBrains Air as running inside a Docker container on a fresh remote virtual machine, separate from the local development environment. The agent can build, test, and install dependencies remotely. You still need to review its changes and handle the resulting branch or pull-request workflow; remote execution is not a substitute for testing and code review.
Copilot in JetBrains Air makes existing Copilot access usable across local agent sessions and Air Teams cloud tasks. Confirm cloud eligibility, repository access, plan billing and review procedures before scaling it to a team.