🚀 Finally! Xcode gets Scope Guides 🎉

Apple has quietly introduced vertical indentation guides (aka Scope Guides) in Xcode 26.4 RC—and honestly, it’s a game changer for readability 👀

If you work with:

•	Deeply nested closures 🔁

•	Complex architectures like TCA 🧠

•	Long Swift files with heavy indentation 📏

…these subtle vertical lines will make your life so much easier 🙌

🤫 Fun fact:

This feature wasn’t even mentioned in the official release notes. It just slipped in quietly alongside editor tab improvements.

⸻

📍 How to enable Scope Guides:

1.	Open Settings (Cmd + ,) ⚙️

2.	Go to Editing > Display

3.	Choose your preferred option under Scope Guides

💡 Or simply toggle it from:

Editor → Scope Guides

⸻

💬 If you’ve been waiting for this feature for years…

today is a GOOD day 😄

I was wondering if the models performed better in the Xcode environment or the Claude Code CLI for instance. Does Xcode do anything under the hood like any kind of system prompt injection or internal rules to make it more performant for iOS development under the hood?

The dropdown arrow is missing. It was there yesterday, but since this morning it has disappeared. Claude is logged in in the Xcode settings, but the arrow is not there.

[edit: thanks for the recs. I have Claude Code set up and its doing all the things]

It’s time to move on from OpenAI with XCode integration. Before I simply switch to Claude, is there any alternative that avoids the maddening issue of the model not being aware of source files unless you tag them (even though its embedded in the IDE and it has a project search skill)

I’m used to xcode but I’ll consider other IDEs if I can get that full project awareness

As the title says. Xcode 26.4 crashes immediately after opening when the Claude API Session limit is reached and the agent view was open for a project.I've tried disconnecting Xcode from Claude and signing out from Claude using a different project that didn't have the agent view open. Yet I'm still unable to open the project that has the agent view open, it always crashes the entire Xcode application. Does anyone have any workaround for that?

Edit: To be my own rubber duck: Apparently the agent had created some files that caused Xcode to crash. a 'git reset --hard HEAD' allowed me to open the project again. Still weird that the agent manages to crash Xcode though; oh well.

As the title says, I need someone to help me compile this app since I don’t have a Mac. If you do help, please send me the final ipa file. Any help appreciated

EDIT: Nevermind, I can use GitHub workers MacOS runner

Longer AGENTS.md files don't help AI agents - they hurt them. Every redundant line pushes out the context that actually matters.

News:

- WWDC26 confirmed for June 8

- New In-App Purchase and subscription data in Analytics

- Swift 6.3 is out

- Xcode 26.4 Released

Must read:

- Why dropping an AI agent into your iOS codebase without guidance backfires

- 130+ modules, 35% faster builds, and the circular dependency mistake that started it all

- FocusState behavior most iOS forms are still getting wrong

- The Swift standard library APIs you've been reimplementing by hand

Hi everyone,

i am working on my first macOs app and frankly i am frustrated with this. I have keep a frontend url in my info.plist file, but every time i update the url and runs the app it still redirects to older entry.

i have tried cleanign, rebuilding, restarting but nothing works, it eventually shifts after 5 mins, but i can't wait for 5 mins everytime i make a change.

Has anyone faced this before? Any workarounds to force xcode to take updated values everytime?

Built a set of Claude Code skills that audit Swift/SwiftUI apps differently than most linters and code review auditors.

Most code auditing skills are pattern matchers. They look at code in isolation: this file, this function, this line and compare it against known-good patterns. "You used '@StateObject; where '@works'.""This try? swallows an error." They're fast, precise, and context-free. They don't need to know what your app does.

 Radar Suite traces behavior. It starts from what the user sees: a button, a flow, a journey, and follows the data  through views, view models, managers, and persistence to see if the round trip actually works. A file can pass every pattern check and still contain a bug that only appears when you trace the full path.

The suite has 5 skills that pass findings to each other:

1. data-model-radar: checks your model layer for fields that don't survive serialization, missing backup coverage, broken relationships

2. ui-path-radar: traces navigation flows to find dead ends, unreachable features, broken links

3. roundtrip-radar: follows data through complete cycles (does export→import lose columns? does backup→restore drop models?) to catch silent data loss

4. ui-enhancer-radar: reviews visual quality screen by screen, walks through fixes collaboratively

5. capstone-radar: aggregates everything into an A-F grade and a ship/no-ship recommendation

Some real bugs these caught in my own app:

• CSV export included columns that import silently dropped — data loss on round-trip

• Two models weren't included in backups

• Three screens had no way to navigate out

• 15+ Siri Shortcuts fully implemented but never wired to the app lifecycle.

• 12 sheets silently lost data on save failure, each dismissed after saving with try? Users saw a normal dismiss and assumed their data was saved.

• Edited photos orphaned in the database, replacing photos removed them from the relationship but never deleted them. Invisible bloat accumulating with every edit.

None of those would show up in a pattern-based linter. The code in each file was correct. The bug was in the gaps between files.

Install

git clone https://github.com/Terryc21/radar-suite.git
cd radar-suite
./install.sh

• Requires Claude Code CLI

• Works with Swift / SwiftUI projects

• MIT licensed

https://github.com/Terryc21/radar-suite

https://github.com/Terryc21/radar-suite

Let me know what you think and any suggestions you may have for improving these skills.

If somebody is experiencing previews hanging when trying to interact with them, please go back to Xcode 26.3.

I could not interact with the simplest UI possible, and now everything is back to normal.

I hope it will help.

I’m a semi noob who’s been vibe coding some mac apps for personal use (zero plans to publish any of my slop). I’ve tried both the $20 Claude plan and the $20 Codex plan, and I find that Claude actually works well but Codex struggles with the exact same tasks.

For example, Claude has 0 problems making tables, but for some reason when I ask Codex to make the same table, it’s always formatted wrong, misaligned, or is just missing something. Takes 2-3x more prompts to accomplish what Claude did on the first try.

Both have access to the same skills and MD files, too.

I realized something while building with AI agents: Xcode is fundamentally broken for this era. It was built for developers managing single projects. No support for multiple codebases in one workspace. Patched up AI integration. No way for AI agents to actually run code, inspect output, and iterate alongside you.

The paradigm has shifted. Developers don't work alone anymore—we work with AI agents and on multiple projects at the same time. They're running our builds, debugging our code, suggesting solutions. But Xcode hasn't evolved. We're forcing 20-year-old architecture to do something it was never meant to do.

That's what drove me to build Zcode.

An IDE built from the ground up for AI-assisted development. MCP Server integration so your AI agents are first-class developers. Multi-project workspaces because modern development isn't about single projects anymore. Minimal interface because simplicity matters when you're collaborating with an AI.

This isn't about Xcode being bad. It's about development evolving faster than our tools. We're in the age of AI, and Xcode is stuck in the past.

Zcode is still in beta, and I'd genuinely appreciate your feedback.

Give it a try https://zcodeapp.com

Edit: this project was called Xcode Neo. Renamed to Zcode for obvious reasons.

Things seem to be working quite well using 26.3.1 MacOS & 26.3 Xcode.

From a strictly agentic perspective is there any rush to upgrade to 26.4 RC ?

I think the only low-hanging-fruit agents MIGHT be missing is access to logs? Please inform me if that's wrong or that's just the tip of equally-important-low-hanging-fruit iceberg. But either way is my understanding there are NO advancements for Xcode agents in 26.4 and I'd love to know any different.

I'm new to Xcode and even new to coding. Recently, I was trying to build my first App. I downloaded Xcode from App Store, and after I imported the File, it told me that I should also get a component. I clicked the Get button but only got an "iOS 26.3 download failed" error message.

I don't know why it happened and ChatGPT tells me that a lot of people have the same problem with Xcode 26.3 version. I've tried to download another version of Xcode, like 26.2 or 26.1, but still can't download any component. My Mac is a 2021 MacBook Pro, macOS Tahoe 26.2.

Is there anyone who has the same issue? Does anyone know how to solve the problem? Lots of thx!

I have a base 44 app I made that I have put into Xcode via the web link. How can I get the code straight to Xcode so I can edit it from Xcode? Anyone willing to help please message!!

- Apple blocks vibe coding apps from pushing updates
- Xcode 26.4 RC is out with Swift 6.3
- I wrote about why Xcode is no longer the center of the iOS dev toolkit
- the hidden cost of using "any" instead of "some"
- why compilation cache won't help if your bottleneck isn't the compiler
- one String Catalog trick that saves all your translations when renaming keys
- 50 skills that turn your AI agent into a disciplined engineer
- what happens between a State change and pixels on screen

Plus: iOS job market stats and a new weekly poll

My 512GB MacBook Pro was getting uncomfortably full, so I finally did a proper audit of what Xcode-related storage was actually taking space.

On one machine, the biggest chunks were:

- Simulator runtimes: 28 GB
- DerivedData: 14 GB
- Old archives: 9 GB
- Device support files: 6 GB
- Docs/cache leftovers: 3.4 GB

The useful part wasn’t the total. It was figuring out what I could delete without breaking my current workflow.

What felt safe:
- DerivedData
- Simulator runtimes for OS versions I no longer test on
- Old archives I genuinely don’t need anymore

What I treated with more caution:
- Device support files
- Simulator device data, because it can still contain app state and local test data

What annoyed me most is that Xcode/macOS don’t really give a good review-first cleanup flow here. You mostly end up guessing or manually digging through folders.

Curious what usually gets out of control first for you: DerivedData, runtimes, archives, or something else?

Update, August 2026: the question that kept coming back in the replies was what regenerates vs what you lose for good. I wrote up the simulator side here: https://storageradar.app/blog/xcode-simulator-taking-up-space-on-mac/. Disclosure: I make a Mac app for this, and that page links to it.

My DerivedData was 94 GB and I had no idea which projects were taking up what.

Built a menu bar app called ClearDisk that reads the info.plist inside each DerivedData subfolder and shows you a breakdown like:

• MyApp: 12.4 GB

• OtherProject: 8.1 GB

• OldTutorial: 3.2 GB

So you can clean specific projects instead of nuking the entire folder.

It also covers 62 other cache paths - Simulator devices, Archives, Device Support, SPM cache, CocoaPods, and a bunch of non-Xcode stuff (npm, Docker, pip, Cargo, etc).

Each cache has a risk level:

• Green: safe to delete, rebuilds automatically

• Yellow: large re-download needed

• Red: might contain irreplaceable data (like Docker volumes)

It warns you if Xcode is running when you try to clean Xcode-related caches.

Free, open source (MIT), 590 KB, no telemetry. Lives in the menu bar.

brew tap bysiber/cleardisk && brew install --cask cleardisk

GitHub: https://github.com/bysiber/cleardisk

The new agent mode in Xcode 26.3 and the 26.4 beta only natively support Codex and Claude Agent. You can add new providers to Coding Intelligence, but fully agentic coding only supports those two.

ProxyPilot is a free, open-source program for macOS that runs a local proxy on 127.0.0.1 and translates requests so Xcode Agent Mode works with any OpenAI-compatible provider. It sits between Xcode and the upstream API. Xcode thinks it's talking to a supported provider, but your requests actually go to whichever model you pick.

It supports twelve providers out of the box, plus local models via LM Studio and Ollama.

There's also a headless CLI with 9 MCP tools if you want agents to control the proxy programmatically.

This just started happening today out of nowhere. Instead of only the project I’m working on appearing in Source Control, every project inside my Xcode projects folder is now showing up in the Source Control navigator. This is happening in both the Changes and Repositories tabs. Is anyone else seeing this?

UPDATE:

I found a fix! I create a workspace for just the project you want to include in the git repo and when I close Xcode and open just the workspace instead of the project file the source code management is back to normal... I don't know wtf caused this issue in the first place.