I've tried pretty much every disk analysis tool (baobab, daisydisk, du), and found them to choke if
1. you create a lot of worktrees in your workflow
2. you use pnpm, uv, and Postgres 18 clone-based database branching
They all think I used 1T+ of my SSD that is only 500GB, because they don't know about APFS clones or hardlinks, they think my node_modules or venv in each worktree takes up 2GB, even though 30 of the worktrees are actually sharing the same 2GB of dependencies
du, honest supports both a web server mode that will serve up an interactive drill-down tree-view of your directories, as well as a CLI that outputs JSON for your LLMs
1. you create a lot of worktrees in your workflow
2. you use pnpm, uv, and Postgres 18 clone-based database branching
They all think I used 1T+ of my SSD that is only 500GB, because they don't know about APFS clones or hardlinks, they think my node_modules or venv in each worktree takes up 2GB, even though 30 of the worktrees are actually sharing the same 2GB of dependencies
du, honest supports both a web server mode that will serve up an interactive drill-down tree-view of your directories, as well as a CLI that outputs JSON for your LLMs