HN Explorer

Ask HN: How is Claude agent experience in Xcode 26.3?

8 points by malshe ↗ HN
I've been vibe coding an iPhone app for educational purposes. The process has been painful because I have to go back and forth between Xcode and Claude Code running in the terminal. I recently learned that Xcode 26.3 natively supports Claude Code and Codex. Has anyone tried it? If yes, please share your experience. I am asking because this means moving to macOS Tahoe which I want to avoid as much as possible.

5 comments

[ 2.1 ms ] story [ 15.7 ms ] thread
[dead] allinonetools_
[flagged]
malshe
Thanks for sharing that. I also checked YT for reviews and found one video that went over the set up step-by-step. I thought it looked pretty good. But I couldn't figure out whether CC has access to the emulator.
Austin_Conlon
I find it more reliable than the Claude Mac app. It also understands the visual output of SwiftUI previews.
nachocoll
The IDE integration question is interesting from a broader vibe coding perspective. Having Claude Code natively in Xcode means the feedback loop tightens — you can see SwiftUI previews alongside generated code, which partly addresses one of the big problems with pure vibe coding: the disconnect between "what was generated" and "what actually behaves correctly."

The emulator access question is key. Vibe coding for iOS without automated visual verification is a bit like building a UI blind — the AI generates syntactically valid code, but you don't know if the layout is broken until you run it. This is where the principle of "Automation must remain verifiable" from the Agile Vibe Coding Manifesto (https://agilevibecoding.org) becomes practical: the closer you can keep human-readable verification to the generation loop, the better the outputs.

For Xcode specifically: tight integration is only better if it still keeps you in the loop reviewing what gets generated, rather than fully deferring to the agent.

fragmede
Hopefully you read this but you can have claude code run xcodebuild from the command line and use osascript and screenshot so you don't need to interact with xcode itself.