Copilot lands in Xcode's own coding assistant: what to check

· 6 min read

#apple-dev#ai

GitHub Copilot now works inside Xcode's own coding assistant. It is a public preview that starts with the Xcode 27.3 beta, and the separate Copilot extension stays, so there are now two ways in.

In short

Xcode 27.2 Xcode 27.3 beta
Release date October 29, 2026 November 3, 2026
Build 27B52 27C5020n
Needs macOS Tahoe 26.6 or later macOS Tahoe 26.6 or later
Copilot in the coding assistant no Coding Intelligence change listed yes, public preview
UI tests with Swift Testing not in the notes supported, with XCUIAutomation
Download format not mentioned in the notes .aea as well, last release with .xip

Then and now

The table shows that the requirement did not move and the coding assistant did. Xcode 27.2's notes have no Coding Intelligence section, so Copilot is the one new name this time. I covered that release in Xcode 27.2 is out: what got fixed, what is still open.

Copilot's road into Xcode has three earlier steps. On October 29, 2024 GitHub opened code completion in Xcode as a public preview, through an extension. On March 11, 2025 Copilot Chat for Xcode became generally available. And Xcode 27, from September 14, 2026, already added Google Gemini and Google Antigravity to the coding assistant, along with Agent Client Protocol support.

How Copilot got into Xcode, step by step Four boxes in order. October 29, 2024: the Copilot extension with code completion. March 11, 2025: Copilot Chat generally available. September 14, 2026: Xcode 27 with Gemini, Antigravity and Agent Client Protocol support in the coding assistant. November 4, 2026: Copilot joins the coding assistant in the Xcode 27.3 beta. A dashed arrow from the last box leads to a box that says the beta needs macOS 26.6 or later. Oct 29, 2024 Extension: code completion Mar 11, 2025 Chat generally available Sep 14, 2026 Xcode 27: Gemini, ACP, Antigravity Nov 4, 2026 Copilot joins the coding assistant, 27.3 beta Needs macOS 26.6+ 1 2 3
From an extension in 2024 to a provider inside Xcode's own coding assistant, with the one requirement that comes with it.

Two ways to run Copilot in Xcode

GitHub's changelog says the integration is set up in Settings > Intelligence in Xcode and that the standalone GitHub Copilot for Xcode extension stays available. It needs macOS Tahoe 26.6 or later, which is also what the beta itself needs. Every Copilot plan is supported. Feedback goes to the GitHub Copilot for Xcode repository or to Apple's Feedback Assistant.

What else is in the beta

What to check before you turn it on

Apple's page on setting up coding intelligence says that an agent can access your project files and other information while it processes requests. It also says that on managed devices an MDM profile can switch the coding assistant off with the key CodingAssistantAllowExternalIntegrations set to false.

That sentence is about agents in general. My take, not fact: assume anything you connect there can see your project, and read what it asks for in Settings > Intelligence before you sign in.

The good and the not-so-good

Good:

Not so good:

My take, not fact: this is worth trying, on a machine and a project where you are happy for the assistant to read the code.

What I would do

My suggestions, not facts:

  1. Install the beta next to your release Xcode, not instead of it.
  2. Open Settings > Intelligence and read the permission text before you sign in to Copilot.
  3. If the extension works for you, there is no rush to move; GitHub keeps it available.
  4. If a script or CI job downloads Xcode, check which format it fetches. 27.3 is the last release with .xip.
  5. If you manage Macs with MDM, look at the CodingAssistantAllowExternalIntegrations key.
  6. Try writing one UI test with Swift Testing on a branch, and XCUIHinge if you target iPhone Duo.
  7. If something misbehaves, report it in the extension's repository or with Feedback Assistant.

Sources