On November 4, 2026, GitHub announced that Copilot is available in public preview inside Xcode’s built-in coding assistant, starting with Xcode 27.3 beta. The existing GitHub Copilot for Xcode extension remains a separate option. If you already use it, you can evaluate the built-in path without assuming the two behave identically.
Check the Mac and the editor first
GitHub and Apple say Xcode 27.3 beta requires macOS Tahoe 26.6 or later. GitHub says all Copilot plans are supported and directs users to Xcode’s Settings > Intelligence to set up the integration. Check which Xcode version is open before looking for that option. Use a disposable project or branch for the evaluation so the beta does not have to become your team’s main build environment.
Compare one change with the same starting files
For a fictional trial, ask each workflow to add a test for an existing Swift function that trims extra whitespace. Give both the same prompt and reset the project between runs. Review which files changed, whether the change stayed in scope and whether the test actually fails when the function is deliberately broken. A test that only passes on the original code may not catch the behavior you care about.
Record the editor version, the workflow used and any cleanup the change required. Compare the actual diffs and test results before deciding whether to keep the extension or try the built-in integration more widely. This is a proposed evaluation; neither workflow was run for this article.
GitHub: November 4 Copilot preview announcement
Apple: Xcode 27.3 beta release notes