// the take
disktree is a keyboard-driven treemap disk-usage visualizer written in Rust with GPUI, built primarily for Omarchy/Hyprland but also shipping for macOS and Windows. It's for developers who want to find what's eating disk space on a local machine or over SSH and delete it with some real safety rails, rather than just another du/ncdu clone.
The deletion path is taken seriously: a dedicated review screen, a removal.rs module with explicit, individually tested refusal rules (mount boundaries, home/system dirs, no shell interpolation, symlinks never followed), and remote delete scripts that verify kernel hostname + machine ID before running. SSH scanning ships static musl-built scanners that get uploaded on demand, checksum-verified, with no sudo or server dependency — a genuinely hard problem solved cleanly. The remote helper streams a depth-first walk to stdout without building a tree in memory, so it scales with open ancestors rather than file count. On Windows, an admin-mode MFT scan beats a full walk by 3-6x, which is a real, measured optimization rather than a marketing claim.
It's built on GPUI, a UI toolkit that itself is young and still evolving (it's Zed's framework, not a stable general-purpose one), so this app inherits that framework's API churn risk. The SSH helper-embedding trick that makes remote scanning dependency-free only works for Linux release builds; macOS and Windows desktop builds don't embed it, so remote scanning from those platforms needs a manually installed disktree-scan binary on the server. The core feature is bulk, cross-filesystem file deletion through a relatively new codebase — the safety checks are well-designed on paper, but a treemap/selection UI that can nuke real data at scale is exactly the kind of feature where a layout or marking-logic bug has an outsized blast radius, and it hasn't had years of real-world mileage yet. It's also fairly tied to Omarchy's theming and workflow, so non-Omarchy users get a capable but secondary experience compared to the primary target.
We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →