GitHub Copilot Reaches Xcode 27.3 Beta and JetBrains Air in a Day Apart, and Air Admins Cannot Cap Spending

GitHub put Copilot inside two editors it does not make on consecutive days: JetBrains Air on November 3, 2026, and Xcode's built-in coding assistant on November 4. The Air version has no way to cap Copilot spending, and the Xcode version is a public preview that needs a beta.

Both announcements are GitHub changelog entries. The two integrations work differently and carry different limits, which is the part the changelog entries leave a reader to assemble.

Xcode 27.3 beta: public preview, macOS Tahoe 26.6

Copilot in Xcode starts with the Xcode 27.3 beta, available from Apple Developer Downloads. It needs a Mac on macOS Tahoe 26.6 or later, and every Copilot plan is supported, GitHub says. To turn it on, open Xcode, then Settings, then Intelligence, and set up GitHub Copilot in the coding assistant.

The separate GitHub Copilot for Xcode extension stays available as an alternative. A Vietnamese-language write-up from nextfuture.io.vn says GitHub has not announced its retirement and recommends keeping the extension as a fallback on a primary machine. That article did not test the integration, and says so.

The changelog does not cover models, usage limits or policy settings for Xcode. It also gives no date for a stable release. The nextfuture article says December, but credits a 9to5Mac report rather than Apple or GitHub, so treat the month as unconfirmed.

JetBrains Air: an Agent Client Protocol agent with gaps

In Air, a user picks GitHub Copilot in the agent picker and the work runs on the Agent Client Protocol, using an existing Copilot subscription. Local tasks need a GitHub Copilot account. Cloud tasks run in a Docker container on a fresh virtual machine and bill against the Copilot plan, not JetBrains AI credits.

Limit in Air	What GitHub's changelog says
Cloud task requirements	JetBrains account in an Air Teams business organization, a Copilot subscription, and an Air administrator who enabled Copilot
Plan choice	Cannot choose per task between a personal and an organization plan
Governance and analytics	Air's analytics do not include Copilot usage
Spending	Admins can disable Copilot by policy but cannot set Copilot spending limits
Failed checks	Subscription checks run when a cloud environment starts, and a failure fails the task

The changelog gives no general availability date, and the plugin link carries the word "alpha" in its name.

The manual route existed on July 18

A guide by Jun Han, listed as a Microsoft software engineer on DEV Community, showed the same connection by hand. It is dated July 18 (the page shows no year) and is part 7 of a series on the protocol.

The entry in Air's acp.json launches npx @github/copilot-language-server --acp. The --acp argument starts the language server as an agent, Han wrote, and other protocol-compatible agents follow the same pattern with a different command.

So the official integration adds a login flow, cloud tasks and billing to something a developer could already wire up in four steps. It does not add governance, since Copilot sits outside Air's analytics. Teams already tracking agent output through tools like the ones in Anthropic's agent memory study or auditing agent skills such as Cloudflare's security audit skill will find that Copilot usage in Air has to be counted somewhere else.

The nextfuture article adds that Copilot can also power Next Edit Suggestions from JetBrains IDEs 2026.2.4. The next thing to watch is whether GitHub's Air entry gains spending limits before the plugin leaves alpha.