Copilot moves into Xcode’s own assistant, no extension needed

GitHub, owned by Microsoft, has put Copilot inside Xcode’s built-in coding assistant. According to the GitHub changelog, the integration is a public preview that starts with Xcode 27.3 beta, and all Copilot plans are supported.

Setup needs a beta Xcode and a recent macOS

GitHub says developers should download Xcode 27.3 beta from Apple Developer Downloads. The Mac must run macOS Tahoe 26.6 or later. Setup happens inside Xcode, under Xcode > Settings > Intelligence, where Copilot can be configured for the coding assistant. GitHub points to Apple’s “Setting up coding intelligence” documentation and the Xcode 27.3 beta release notes for details.

The changelog describes this as another way to use Copilot in Xcode, not a replacement. The existing GitHub Copilot for Xcode extension stays available as a separate option, so teams can keep their current workflow or switch to the native one. Feedback goes either to the GitHub Copilot for Xcode repository or to Apple Feedback Assistant.

Because it is a preview tied to a beta toolchain, it is not meant for production machines yet. The announcement does not say when it will reach a stable Xcode release, and it gives no pricing beyond saying every Copilot plan is covered. It also does not list which models or agent features are available in the Xcode integration, or whether usage counts against premium request allowances. Those points are not established by the source.

Native assistant instead of an add-on

For Xcode users the practical difference is where Copilot lives. The older extension is a separate add-on. The new route plugs Copilot into the assistant that Apple ships with the IDE, which means Copilot sits in the same place as Apple’s other supported tools. GitHub’s own wording is that it brings Copilot “into your native Xcode workflow”.

That matters for teams that already pay for Copilot across several editors. A developer on an existing Copilot seat does not need a new plan to try it, according to GitHub’s statement that all plans are supported.

A pattern of Copilot following other agents into IDEs

The announcement fits a strategy of making Copilot an option wherever developers already work, rather than only in its own editor. Apple opened Xcode to outside agents earlier this year: Xcode 26.3, released in February 2026, added agentic coding with Anthropic’s Claude Agent and OpenAI’s Codex, and exposed Xcode’s capabilities over the Model Context Protocol so other compatible agents can connect, as 9to5Mac and SD Times reported. Copilot now arrives in the same assistant as those rivals.

It is also the second IDE integration of this kind in two days. On November 3, GitHub added Copilot to JetBrains Air, and cloud tasks there are billed to the user’s Copilot plan rather than JetBrains credits. Air launched in a March 2026 public preview with Codex, Claude Agent, Gemini CLI and JetBrains’ Junie, so Copilot is again joining an existing field of agents instead of leading it.

The move also shows how GitHub is treating billing and usage as a platform-wide concern. Only a day earlier it added reporting that lets organizations separate own-key traffic from Copilot-hosted models in the usage API. Whether the Xcode integration shows up in that reporting is not stated.

For Apple developers, the choice is now wider: Claude Agent, Codex and Copilot can all be reached from Xcode’s assistant, and Copilot users can pick between the native route and the extension. How the two Copilot paths compare in features and speed is something GitHub has not spelled out, and the claims here come from GitHub’s changelog rather than independent testing.