Support
Something odd, or a verdict that looks wrong? Start here. If it is still broken, send feedback with the reasons Crumbs showed, or open an issue on GitHub.
Feedback form built with Makeform.
Will Crumbs delete my work?
Crumbs never deletes: it moves items to the Trash. Worktrees with uncommitted files, folders a process is using, and anything changed in the last 24 hours are marked Keep and cannot be selected. Right before trashing, it checks every item again and skips anything that changed since the scan.
A worktree has commits that are not merged. Why is it still Safe?
Moving a worktree to the Trash removes the checkout, not the branch. The branch and its commits stay in the main repository. Only detached checkouts with commits no branch has are kept.
Why is something marked Check?
Crumbs could not fully vouch for it: it changed recently, holds a secret-looking file that differs from the main checkout, or its git metadata is gone. Select a row to see every reason.
Can I change how long things wait before they count as safe?
Yes. Settings → Rules lets you set the waiting period for each kind, like 60 days for node_modules, or switch a kind off entirely.
The first scan is slow.
Measuring hundreds of gigabytes means reading the metadata of millions of files, so a first scan can take a minute or two. Results appear as they are measured, and the last scan loads instantly next time.
Crumbs missed a kind of leftover my tools make.
Rules are small JSON files in the repository. Open an issue or a pull request with the folder pattern and how to tell it is safe.