GitHub Copilot comes to JetBrains Air over the Agent Client Protocol, with cloud tasks billed to the Copilot plan instead of JetBrains AI credits
Another agent host opens up to Copilot through ACP, but spending controls and usage reporting stay on the GitHub side.
// Key points
- Select GitHub Copilot in Air's agent picker and use an existing Copilot subscription; track several agent sessions in parallel and review changes next to the code
- Cloud tasks run through Air Teams in a Docker container on a fresh virtual machine, with all traffic through a proxy and no state carried between tasks
- You cannot choose whether a task uses a personal or an organization Copilot plan, Air's analytics do not include Copilot usage, and Air admins can disable Copilot but cannot set Copilot spending limits in Air
Builder's takeACP is turning the IDE into a picker for whichever agent you already pay for. The catch is in the fine print: no plan selection and no spending limits inside Air. If a team adopts it, set Copilot budgets on the GitHub side before turning on cloud tasks, and expect Air's dashboards to miss that spend.
// Background · from #Coding agents
Full timeline →- Nov 4 Dependabot version updates now support Agent Package Manager, opening pull requests for agent skills, prompts and instructions declared in apm.yml
- Nov 4 CWE-bench v2 opens 100 vulnerability-fixing tasks across 91 CWEs: Gemini 4 Argon leads at 67.8% pass@1, Claude Opus 5.5 at 67.3%, DeepSeek V4.1 Flash reaches 57.0% at $0.04 a rollout
- Nov 3 GitHub Actions will block pull_request_target by default in public repositories from December 2, with brownouts on November 9 and 16