Apple stopped picking your AI coding agent for you — Xcode now takes any of them
Xcode 26.6 added Google Gemini alongside Claude Agent and OpenAI Codex as built-in AI coding assistant options, and opened the door to any compatible tool via the Agent Client Protocol — a sign that 'which AI coding agent' is becoming a genuine build decision for iOS teams, not a single vendor default.
1 August 2026
Xcode 26.6, shipped in late June 2026, added Google Gemini as a built-in AI coding assistant option, joining Anthropic’s Claude Agent and OpenAI Codex, which Apple had already integrated. The more consequential change sits underneath that headline: the update also enables the Agent Client Protocol, an open standard that lets any compatible AI coding agent plug directly into Xcode, not just the three Apple has pre-wired.
Six months ago, choosing to build for iOS meant accepting whatever AI tooling Apple had bothered to integrate, if any. That’s no longer true. A team building a native iOS app can now genuinely pick its coding agent on merit — reasoning quality, cost, how it handles Swift and SwiftUI specifically — rather than defaulting to whatever ships in the box, and switch later without re-platforming the whole workflow.
So what
For anyone commissioning an iOS build, this closes off a question that used to be a legitimate blocker: “does our team’s AI tooling of choice even work properly inside Xcode?” It now generally does, or can. That doesn’t change the fundamentals of what makes a good iOS partner — Swift expertise, App Store process knowledge, a track record of shipped native apps — but it does mean AI tooling choice is no longer a reason to compromise on any of those. If you’re scoping a native iOS build and want a team that can tell you exactly which AI tooling is doing what in your codebase, see our iOS & Android work or get in touch to talk through the project.