JetbrainsVladimir GromozdinAnnouncement
Use Your GitHub Copilot Plan in JetBrains Air – in Your IDE and in the Cloud
Summary
GitHub and JetBrains have integrated GitHub Copilot into JetBrains Air, an agentic development environment that lets users hand coding tasks to agents and review changes in one place. Users can select GitHub Copilot as the agent, running locally in the JetBrains IDE via the Agent Client Protocol (ACP) or in the cloud with Air Teams. Tasks use the user’s existing GitHub Copilot subscription, not JetBrains AI credits, and run the official GitHub Copilot CLI. Cloud tasks execute on isolated virtual machines, allowing Copilot to continue working after the user closes their laptop, with all traffic proxied and no state carried between tasks. Air also supports automations, such as scheduled dependency updates or pull request reviews, using the same Copilot plan, though users must monitor their own credit usage on GitHub.
Context
JetBrains Air is an agentic development environment that allows users to hand coding tasks to agents, run them in parallel, and review changes in one place. This post announces the integration of GitHub Copilot as an agent in Air, supporting both local execution in the JetBrains IDE and cloud execution with Air Teams, using the user’s existing GitHub Copilot subscription.
Approach / What changed
The integration uses the Agent Client Protocol (ACP) to connect the official GitHub Copilot CLI to JetBrains Air. Users select GitHub Copilot as the agent in Air, and tasks run on the user’s existing Copilot subscription. For cloud tasks, Air provisions an isolated virtual machine with a Docker container running Copilot, with all traffic proxied and no state carried between tasks.
Takeaways
GitHub Copilot can be used as an agent in JetBrains Air via the Agent Client Protocol (ACP), running locally in the IDE or in the cloud with Air Teams.
Cloud tasks run on isolated virtual machines with proxied traffic, allowing Copilot to continue after the user closes their laptop.
Air supports automations like scheduled dependency updates or pull request reviews using Copilot, but users must monitor their own credit usage on GitHub as Air does not track or limit Copilot credits.
FAQ
How is GitHub Copilot different from other agents in Air?
GitHub handles the Copilot account and credit tracking. Air does not show Copilot usage or set spending limits, so users must monitor their credits on GitHub.
Which GitHub Copilot plans can I use?
Any plan that GitHub accepts for the Copilot CLI. Air does not check which specific plan you are using.
Why did my task fail soon after it started?
Most likely your GitHub plan has no credits left. Air checks for an active Copilot subscription before starting a task but cannot see remaining credits. Check your usage on GitHub.
Source and freshness
- Source
- blog.jetbrains.com
- Published
- Added to Yomu
Summaries are generated from the original by a language model. Check the original before relying on it.
Keep reading
Related reading
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
The best engineering reads, once a week
One useful email. Unsubscribe anytime.