Brifing

GitHub Copilot Integration with JetBrains Air for IDE and Cloud

Run GitHub Copilot agents locally or in the cloud using JetBrains Air workflows.

The JetBrains Blog2 min

1GitHub Copilot Joins Air

GitHub Copilot is now available as an agent within JetBrains Air, allowing developers to execute coding tasks locally or in the cloud. This integration utilizes the Agent Client Protocol to connect the official Copilot CLI. Users can now manage Copilot tasks alongside other agents like Claude, Codex, and Junie.

2Local Execution Workflow

Developers can run GitHub Copilot locally within their JetBrains IDE by selecting it in the agent picker. This process requires an active GitHub Copilot subscription but does not consume JetBrains AI credits. Once a task is described and sent, the agent operates directly within the local project environment for immediate review.

3Cloud-Based Task Execution

With Air Teams, GitHub Copilot tasks can run in the cloud, enabling developers to close their laptops while the agent continues working. Each task is assigned a dedicated virtual machine and runs inside a sandboxed Docker container. This ensures that builds, tests, and package installations remain isolated from the local machine.

4Cloud Setup Requirements

To initiate cloud tasks, users need a JetBrains account linked to a company using Air Teams and an active GitHub Copilot subscription. Tasks must be started from a remote branch, requiring developers to push their changes before execution. Air handles authentication through a unified GitHub connection within the VCS Providers settings.

5Automated Task Scheduling

Air allows for the automation of GitHub Copilot tasks based on specific schedules or repository events like pull requests. While convenient, developers should monitor usage carefully, as frequent automated runs can quickly deplete Copilot credits. Air does not provide internal warnings when credit limits are reached, so tracking remains a manual process.

6Resource Isolation Mechanism

Every cloud task operates in a fresh virtual machine environment to maintain security and consistency. All network traffic is routed through a proxy, and no data or state carries over between different task executions. This architecture ensures that complex operations like dependency updates do not impact the host development environment.

7Subscription and Credit Management

GitHub manages all Copilot account details, including plan status and remaining credits. Because Air does not track or limit Copilot usage, users must monitor their consumption directly on the GitHub platform. If a task fails shortly after initiation, it is likely due to insufficient credits remaining on the active subscription plan.

8Strategic Implementation Advice

For teams adopting this integration, starting with well-defined, small tasks like flaky tests or dependency bumps is recommended. This approach allows for easier review and predictable credit usage compared to full pull request automation. By leveraging existing Copilot plans, teams can scale their development efficiency without incurring additional JetBrains AI costs.

Original article: The JetBrains Blog — GitHub Copilot Integration with JetBrains Air for IDE and Cloud