Xcode 27 Is Out: Apple Silicon Only, Swift 6.4, Agents

Apple released Xcode 27, the first version to drop Intel Mac support entirely, requiring Apple Silicon hardware to build for iOS 27 as of today. The release ships with Swift 6.4, native support for Claude, Gemini, and GPT-4o agents using developers' own API keys, and an install roughly 30% smaller than Xcode 26, while requiring macOS Tahoe 26.4 or later. GitHub's Xcode 27 runner image is arm64-only, so CI/CD pipelines must migrate to xcode-27 or xcode-27-xlarge runners.

Xcode 27 is out today. It ships with Swift 6.4, bundles Claude, Gemini, and GPT-4o natively, and cuts Intel Mac support entirely. If you’re not on Apple Silicon, you cannot build for iOS 27 starting today. Intel Is Out — This Is the Real News This is the first Xcode to fully drop Intel support. Not a soft deprecation, not a compatibility warning — the installer won’t run on Intel hardware at all. Apple’s justification is straightforward: the on-device Neural Engine powers code completion and the new autonomous debugging features, and that silicon only exists in M-series chips. The good news: you can still ship to Intel users. The macOS 27 SDK supports Universal apps that back-deploy to macOS 12 and later. You build on Apple Silicon, and your app runs on Intel just fine. What you can’t do is build those apps on an Intel Mac anymore. CI/CD teams take note. GitHub’s Xcode 27 runner image is arm64-only https://github.blog/changelog/2026-09-10-xcode-27-runner-image-now-runs-on-macos-27/ . The Intel macOS runner pool cannot run this image. If your pipeline still includes Intel runners, you’re now managing two runner shapes. The fix: migrate to xcode-27 or xcode-27-xlarge in your runs-on value and confirm you’re on an arm64 runner. Agents in the IDE — Three Models, Your Keys, One Useful Command Xcode 27 supports Claude, Gemini, and GPT-4o natively. You bring your own API keys and pay Anthropic, Google, or OpenAI directly. Apple doesn’t sit in the middle. Inline autocomplete is local — it runs on the Neural Engine and your source code never leaves the machine. The heavier agentic work refactoring across files, test generation, long-horizon tasks routes to the cloud model you’ve chosen, but only when you explicitly opt in. The feature worth knowing: /plan . Before the agent touches a single file, you issue /plan in the conversation pane. The agent scopes the work, shows you what it intends to change, and waits for confirmation. This directly fixes the “agent ran off and rewrote 40 files” failure mode that made agentic IDEs frustrating. If you’ve built MCP servers for your tools, they work inside Xcode without modification. Swift 6.4: Two Changes Worth Your Attention Xcode 27 ships with Swift 6.4. Most of the release is refinement, but two changes are worth calling out. SE-0520 catches a real silent bug: if you create a throwing Task and ignore the returned handle, the error vanishes. Swift 6.4 now emits a warning. This is the kind of fix that saves you an afternoon of debugging a production issue that reproduces intermittently. Async in defer finally works. You can now await inside a defer block, which removes a long-standing workaround pattern for cleanup code in async functions. Foundation also gets a URL parsing speed improvement — up to 4x faster — and the Swift Concurrency instrument now surfaces actor contention and async task scheduling data in a usable form. Smaller Install, Better Device Testing Xcode 27’s install is roughly 30% smaller than Xcode 26. On a CI runner that provisions fresh each build, that’s real time saved. The tradeoff: macOS Tahoe 26.4 or later is required. If your runners are on an older macOS release, that update comes first. Device Hub gets a meaningful upgrade: simulators, physical devices, and system state testing are now in a single window. iPhone Duo support is included — you can test the foldable device’s four poses open, close, rotate, fold without hardware, using the new simulator controls in Device Hub. What to Do Now - On Intel? You need Apple Silicon to build for iOS 27. There is no workaround at the IDE level. - Update your CI/CD: Switch to runs-on: xcode-27 arm64 . Audit for any remaining Intel runner references. - Upgrade macOS first: Xcode 27 requires macOS Tahoe 26.4+. Runners and local machines need this before Xcode can install. - Set up agentic coding: Go to Intelligence settings in Xcode, add your API key for whichever model your team prefers. Local autocomplete works without a key. - Check Swift 6.4 warnings: Run your project. SE-0520 warnings for ignored Task handles may surface — fix them, they’re real bugs. The Intel cutoff is the right call technically — the Neural Engine advantage is real. It’s also blunt. Apple could have offered a longer transition window or a compatibility tool; they didn’t. Full Xcode 27 release notes are on Apple’s developer portal https://developer.apple.com/go/?id=xcode-27-sdk-rn , and the WWDC26 session covers the agentic coding architecture in detail https://developer.apple.com/videos/play/wwdc2026/258/ . If you’re building iOS apps, the hardware question is no longer something you can defer.