1. AI‑powered “agentic coding” is a mixed blessing
- “Xcode is using the Claude Agent SDK, which means that you get the full power of Claude Code directly in Xcode—including subagents, background tasks, and plugins—all without leaving the IDE.” – CharlesW
- “I find the existing agentic coding integration to be clunky and slow.” – etothet
- “I’m still not convinced that the AI is useful; I prefer to keep the agent separate from the IDE.” – forrestthewoods
2. Xcode’s performance and reliability remain a pain point
- “Xcode really needs a couple of years of pure bugfix.” – flohofwoe
- “The debugger variable view panel is so bare bones that it looks like it was ripped out of an 80’s home‑computer program.” – flohofwoe
- “The debugger can lock up and break breakpoints after a few steps.” – Aloisius
3. File‑type hijacking and installation bloat frustrate developers
- “Xcode re‑associates its preferred filetypes every time you update it.” – bandrami
- “The hijacking of file associations is one of the most awful and malicious things about macOS.” – walthamstow
- “Xcode installs a bunch of gigantic, multi‑gigabyte artifacts for iOS runtimes that fill up the hard drive and can’t be deleted because of SIP.” – mikenew
4. Many developers prefer other IDEs or a split‑tool workflow
- “I use VSCode for day‑to‑day coding and Xcode only for building and debugging.” – seankit
- “I prefer a lightweight editor with IntelliSense, a separate build system, a visual debugger, and a CLI coding agent.” – forrestthewoods
- “I’m happy with Xcode for iOS, but it’s too slow and feels different from other major IDEs.” – indycliff
These four themes capture the bulk of the discussion: the promise and pitfalls of AI integration, ongoing performance woes, the annoyance of file‑type and installation quirks, and the continued preference for alternative tooling.