FindDiskKiller 1.3.7
FindDiskKiller 1.3.7
This release adds verified cleanup for rebuildable Codex and Claude caches,
tightens official chat cleanup estimates, and makes the selected in-app
language authoritative for all locale-sensitive values.
Improvements
- Discover Codex CLI cache and temporary directories for the default,
environment-configured, and user-added Codex homes. - Discover verified Codex and Claude Desktop cache roots in Application
Support and the standard macOS Caches directory. - Offer each verified cache root through Safe Cleanup with exact path and inode
revalidation, Trash recovery, and the existing non-blocking background
refresh workflow. - Keep cleanup available for custom Codex homes after their parent data source
has been revalidated. - Use the app-selected language for durations, dates, relative times, counts,
percentages, and localized storage sizes even when the macOS system language
is different. - Keep system error presentation, loading placeholders, source names, and
human-readable PDF history exports aligned with the app-selected language;
CSV exports retain their stable machine-readable schema.
Accuracy and safety
- Limit the Codex "release immediately" estimate to conversation rollout
files undersessionsandarchived_sessions. Associated shell snapshots
and visualizations remain visible as retained data until an authoritative
rescan confirms their removal. - Classify Claude
.claude/backupsas protected configuration recovery data,
never as a rebuildable cache. - Deduplicate cache aliases by physical identity and exclude nested cache roots
from their protected parent scans so every byte is counted once. - Keep browser partitions, HTTP storage, authentication, configuration,
conversations, skills, plugins, worktrees, databases, and Claude VM bundles
protected. VM bundles can contain mutable user session state and are not
offered for cleanup.
Release integrity
- Build 129 passed the complete serial Swift test suite and the CI-equivalent
suite, including cache discovery, physical-byte conservation, cleanup path
identity checks, continuous cleanup during refresh, official provider
fixtures, and localization completeness checks for all ten shipped
languages. - The release build is universal, signed, notarized, Gatekeeper-validated, and
Sparkle-signed before publication.