Hi,
I've been using Xcode with Codex. I have come to the conclusions that the only window I need open 99.8% of the time is the AI conversation window. After working with this setup for almost a month duration and 80 hours of actual work, I don't bother to look at any of the code. I look at the results and guide Codex to design and implement and help debug.
The fact that the AI window acts like a standard coding window is a mistake on the Xcode designers part. That window should never be closed or replaced if you happen to try to look at a file. That window is not the main focus for Xcode in the hands of an expert iOS developer. Yes I will place myself in the category, even though I don't know everything about iOS development.
The entire approach is a shocking change for me, as I assume it is for others. I'm in awe of how well Codex works with Xcode and/or the MacOS command line tools.
This brings up another point, it seems the Codex does most of it's work via the command line. I'm not sure I like this, but the productivity benefits are overwhelming.
Codex and likely other AIs need better Xcode support for file access. I'm not sure what that means, but I'll bet Xcode engineers and designers know exactly what I mean.
I'm now 10x more productive, working on a full stack project. iOS with SwiftUI and SwiftData and a server component with Vapor and Swift. Working inside a workspace. Killer!!