Kyle HughesNov 30
Xcode is several generations behind the latest AI-assisted programming tools. I’m not sure how they catch up at their cadence, but the vertical integration Apple has should be the greatest advantage here. The AST should be exposed to an agent to allow symbol navigation; it should have access to structured diagnostics; the entire documentation surface for all symbols should be available. The harness they could build is amazing. I don’t know if they want to.
https://mastodon.pepicrft.me/@pedro/115633547285745211
Pedro Piñera (@[email protected])

@swiftlang's swift-build being open source means we get build-time data at build time. Info that never surfaces in .xcresult, .xcactivitylog, or xcodebuild logs. We forked it to output structured data to SQLite. Tested on @[email protected] iOS and @[email protected] . Agents identify bottlenecks, parallelization issues, and surface actionable warnings. Open-sourced as Argus. Install via mise, set XCBBUILDSERVICE_PATH, configure agent memory. https://tuist.dev/blog/2025/11/27/teaching-ai-to-read-xcode-builds

Mastodon
Show threadMatt Massicotte
@kyle Most of this is accessible via SourceKit-LSP right now
Nov 30 at 2:03amMona for iPhone
Show threadKyle HughesNov 30
@mattiem yes, and the community will build plenty of tools around this, but the “I” in IDE is the selling point!
Show threadDaniel LyonsNov 30
@kyle @mattiem Apple has the advantage for Xcode Cloud as well, and yet it seems to always crash.
Show threadKyle HughesNov 30
@dandylyons @mattiem I just can’t get it out of my head that they are incentivized to make my builds slow :(
Show threadDaniel LyonsNov 30

@kyle @mattiem Yeah you're totally right. It's like paying a plumber by hour.

In Xcode Cloud's case I don't think you even get to decide what hardware, OS, and region your build happens on.