ShipIt Cache Clear — 2026-06-12

Status: Complete (done, no follow-up required)

Importance: Medium — routine maintenance, but warning threshold tripped.

Cleared

• ~/Library/Caches/com.microsoft.VSCode.ShipIt — 1,061,024 KB (~1036 MB / 1.01 GB). VS Code Squirrel/ShipIt updater cache. Safe; regenerates on next update check.

Totals

• Total freed: ~1036 MB (1.01 GB)
• Disk available after: 112 GB (was 111 GB)
• Errors: none. Delete confirmed; no remaining *ShipIt* dirs under ~/Library/Caches.

[WARNING: unusual ShipIt growth]

A single VS Code ShipIt cache hit ~1.0 GB in one daily cycle (normal is tens of MB). Likely a large or repeated staged update, or an orphaned payload from an interrupted VS Code update. Not dangerous. Watch item: if com.microsoft.VSCode.ShipIt reappears at 500 MB+ tomorrow, VS Code is probably re-staging updates repeatedly or an update keeps failing to apply.

Run notes

• Deletion required the Desktop Commander host-shell fallback (cowork bash sandbox cannot mutate ~/Library in unsupervised mode) — exactly as the drift-guard spec anticipates.
• Codex log: /Users/samaguiar/Documents/Codex/system-maintenance/shipit-2026-06-12.md

Post-run QA reflection

• Ran cleanly: pre-flight (spec + vault on first path), scan, sized delete, disk re-check, logs.
• Errored paths: none.
• Warning threshold: HIT (1036 MB > 500 MB).
• Suggested next-run adjustment: track VS Code ShipIt size day-over-day; if it stays >500 MB, surface a prompt to check the VS Code update channel for a stuck re-stage.