zlacker

>>davidb+(OP)
When do you actually need to open Xcode if you have XcodeBuildMCP [0]?

I haven't opened Xcode in months. My terminal: Claude writes code. build_sim. launch_app_sim. screenshot describe_ui.

What still requires Xcode: Instruments profiling, Signing/provisioning

For UI iteration, describe_ui returning the accessibility tree might actually be more useful to an agent than a preview screenshot.

>>anupam+Sg
Multiple config files of Xcode projects are not publicly documented as far as I remember and personally I have preferred to require my agents not to modify them out of fear it might break something and be hard to fix. I don't know how agentic programming will work in Xcode but I would expect it to do it using a safer approach, so that's also another case where it might have an advantage.

Your workflow looks very interesting especially the describe_ui part, are you already able to do this today?

>>Millio+1t
I've been using tuist plus codex cli and vscode. only using Xcode for running and debugging. I would love to get rid of xcode entirely. The tuist plus xcode project is a tiny shim - the rest of the app is in spm packages.

Tuist generates the code project from a simple swift confiuration file similar to Package.swift. I don't know why apple can't just throw away the proprietary and ugly Xcode project files and provide a sane build system that would work in any IDE, on the command line, in CI and now with AI agents.

They could open up the instruments format while they are at it for the same reason, do they really gain anything by making it proprietary?