Honest accounting and safe relocation of the disk space Apple developer tooling consumes — simulator runtimes, CoreSimulator, DerivedData, device support, caches, archives — while keeping Xcode, simctl and devicectl working. Evidence-gated: no strategy is called supported until it is measured.

4 Open Issues Need Help Last updated: Sep 18, 2026

Open Issues Need Help

View All on GitHub

Honest accounting and safe relocation of the disk space Apple developer tooling consumes — simulator runtimes, CoreSimulator, DerivedData, device support, caches, archives — while keeping Xcode, simctl and devicectl working. Evidence-gated: no strategy is called supported until it is measured.

Swift
documentation help wanted evidence from-review

Honest accounting and safe relocation of the disk space Apple developer tooling consumes — simulator runtimes, CoreSimulator, DerivedData, device support, caches, archives — while keeping Xcode, simctl and devicectl working. Evidence-gated: no strategy is called supported until it is measured.

Swift

Honest accounting and safe relocation of the disk space Apple developer tooling consumes — simulator runtimes, CoreSimulator, DerivedData, device support, caches, archives — while keeping Xcode, simctl and devicectl working. Evidence-gated: no strategy is called supported until it is measured.

Swift
good first issue architecture from-review

Honest accounting and safe relocation of the disk space Apple developer tooling consumes — simulator runtimes, CoreSimulator, DerivedData, device support, caches, archives — while keeping Xcode, simctl and devicectl working. Evidence-gated: no strategy is called supported until it is measured.

Swift