GitHub announced two extensions of Copilot’s reach back to back, on November 3 and 4, 2026. JetBrains Air now lets developers pick Copilot as the agent for local or cloud coding sessions, and Xcode 27.3 beta’s built-in coding assistant now offers Copilot as a native option, alongside the existing dedicated extension.
Copilot built into Xcode’s coding assistant
The first announcement, published on November 4, opens Xcode 27.3 beta’s built-in coding assistant to Copilot. This integration is separate from the existing “GitHub Copilot for Xcode” extension, which stays available — Apple developers now have two paths into Copilot inside their IDE. The feature is in public preview, reachable from Xcode under Settings then Intelligence, and requires macOS Tahoe 26.6 or later.
JetBrains Air: local sessions and cloud agents
The second announcement, published the day before, concerns JetBrains Air, JetBrains’ coding-agent environment. Air introduces an agent picker where Copilot now sits alongside the other options, with two execution modes: locally inside the IDE, or in isolated cloud environments through Air Teams, driven from the IDE or a browser.
| Criterion | Xcode (preview) | JetBrains Air |
|---|---|---|
| Status | Public preview | Available |
| Execution | Local, inside the built-in assistant | Local or cloud (isolated container) |
| Protocol | Not disclosed | Agent Client Protocol (ACP) |
| Requirements | Xcode 27.3 beta, macOS Tahoe 26.6+ | Copilot account; Air Teams organization for cloud |
| Billing | Existing Copilot subscription | Copilot subscription, not JetBrains AI credits |
On the architecture side, JetBrains Air’s cloud tasks run inside a Docker container on a fresh virtual machine, with all traffic routed through a proxy and no state kept between tasks. The integration relies on the Agent Client Protocol, an open protocol that standardizes JSON-RPC exchanges between an IDE and a coding agent, in a spirit not unlike what the Model Context Protocol does on the tool- and data-access side.
{
"jsonrpc": "2.0",
"method": "initialize",
"params": {
"protocolVersion": "1",
"clientCapabilities": { "fs": { "readTextFile": true } }
}
}Two openings in two days, across two IDEs that compete with VS Code, say more about Copilot’s strategy than any press release: being present wherever developers write code is becoming more important than pushing its own editor.
What it means for mixed teams
For a team mixing Xcode on the mobile side with JetBrains IDEs on the back end, the news makes it possible to unify the coding agent without forcing a single editor or juggling separate AI agent subscriptions depending on the workstation. Air’s cloud tasks in particular let teams run builds, tests and package installs without touching the developer’s local environment, an approach not unlike GitHub’s own background agents.
Key takeaways
Within 48 hours, Copilot gained a native presence in two IDEs that don’t belong to Microsoft, across two different execution models: local in Xcode, local or cloud in JetBrains Air. Neither integration changes developer-side billing, which still runs on the existing Copilot subscription.
What stands out most in these two announcements is how little fuss surrounds compatibility: Copilot is no longer trying to convert developers to VS Code, it’s installing itself wherever they already work. For an agency juggling Xcode and JetBrains IDEs across engagements, that’s a genuine operational comfort — as long as someone keeps an eye on consumption, since cost governance stays separate from IDE governance. — Simon Janvier
Further reading: official announcement for JetBrains Air and official announcement for Xcode on the GitHub changelog.
