Build intermediates
Can I delete Build/Intermediates.noindex?
Build intermediates are generated during compilation, but nearby Xcode folders can hold different evidence and outputs with different recovery costs.
The bounded answer
BuildSweep 1.0 can classify the exact Build/Intermediates.noindex leaf as rebuildable. It does not generalise that decision to the whole Build folder, Archives, products, test results, or source packages.
A safer review sequence
- 1Stop active builds before reviewing intermediates.
- 2Confirm the exact leaf is Build/Intermediates.noindex within supported DerivedData.
- 3Keep Archives, test results, products, packages, and source outside the action plan.
- 4Review, revalidate, and move to Finder's Trash rather than permanently deleting.
Check the storage shape locally
Use the manual planner without sharing paths, project names, inventories, or exact values with VaultDevLabs.
Open the Xcode storage planner →Primary references and product boundary
- Apple: Running tests and interpreting results
- Apple: Distributing apps for beta testing and releases
- Apple: Managing files and folders in an Xcode project
Apple documents Xcode archives, test-result bundles, and project-file operations. The exact two-leaf action boundary described here is BuildSweep 1.0's deliberately narrower product policy, not a claim that Apple designates every DerivedData item as safe to remove.
Diagnose before you move anything
BuildSweep reviews supported Xcode-generated storage locally and requires an exact frozen plan before selected leaves move to Finder's Trash.
View BuildSweep in the Mac App Store