Copilot now runs inside JetBrains Air

What changed

Air lists GitHub Copilot alongside its other agents, and the work runs on your existing Copilot subscription. The connection uses the Agent Client Protocol (ACP), and you can keep using the regular GitHub Copilot plugin next to it.

What you can do

• Track several agent sessions at once, with project context and IDE tools, and review changes alongside your code.
• Run Copilot cloud tasks through Air Teams from your IDE or a browser. They use your Copilot plan rather than JetBrains AI credits.

How to start

1. For local tasks, install Air in your JetBrains IDE.
2. Select GitHub Copilot and connect your Copilot account.
3. For cloud tasks, you need a JetBrains account in an Air Teams-enabled business organization, and your Air administrator has to turn Copilot on. In a browser, connect GitHub under Settings > VCS Providers. In the IDE, pick Cloud from the environment selector.

Before you lean on cloud tasks

Each cloud task runs in a Docker container on a fresh virtual machine, with all traffic going through a proxy and no state kept between tasks.

Air may check your subscription or credits only when the cloud environment starts, so a task fails with an error in the session if they aren’t available. You can’t choose whether a task uses your personal plan or your organization’s plan.

Air’s analytics don’t include Copilot usage, and Air admins can turn Copilot off but can’t set Copilot spending limits there.