Skip to content

FindDiskKiller 1.2.0

Choose a tag to compare

@jianyintang jianyintang released this 29 Jul 15:26
· 146 commits to main since this release

FindDiskKiller 1.2.0

This release adds AI Storage analysis and safe cleanup for supported Codex and
Claude Code conversations, with explicit user control over every scan and
deletion.

Highlights

  • Analyze Codex and Claude Code storage in parallel, grouped by provider,
    project, conversation, subagent, and file category.
  • Start or refresh analysis only after an explicit click. Opening AI Storage,
    navigating back to it, rebuilding the view, or waking the Mac never starts a
    scan automatically.
  • Distinguish physical disk measurement from conversation attribution quality,
    with structured diagnostics that explain incomplete or ambiguous data.
  • Review and permanently delete selected supported conversations through the
    providers' official interfaces. Active, changed, incompatible, and
    unsupported conversations are skipped rather than force-deleted.
  • Batch-select conversations by age and filters, review provider capabilities,
    immediate releasable bytes, logical cleanup, and retained project data before
    confirming deletion.

Improvements

  • Keep cached results interactive while an explicit refresh is running and show
    real scan phases and processed counts without fabricated percentages.
  • Improve project attribution, responsive layouts, narrow-window navigation,
    thread details, filters, selection controls, and cleanup result reporting.
  • After a successful cleanup, hide stale measurements and show a dedicated
    completion summary until the user chooses to analyze again.
  • Avoid navigation skeletons when AI Storage has no data to load, eliminating a
    flash when switching into the feature before the first analysis.

Safety and limitations

  • AI Storage scans remain read-only and do not checkpoint or modify provider
    databases. Cleanup never falls back to direct SQLite writes or manual file
    deletion when an official provider operation fails.
  • Claude Desktop and Cowork conversations must still be deleted in Claude
    Desktop because no stable public third-party deletion interface is available.
  • Database row deletion may be a logical cleanup without immediately shrinking
    the SQLite file; only verified exclusive file allocations are reported as
    immediately releasable space.