Cleanator 0.2.0

Cleanator 0.2.0 — a module of the Blackberrylabs control tower.

Cleanator joins the Blackberrylabs family's control tower: one screen that gathers what Cleanator, MCProster and Permitt find on a machine, most serious first. Nothing changes in what Cleanator proposes or how.

New

• cleanator-cli report [path]: the classified scan as a bbl-report/1 document (always JSON; the home directory by default). One finding per rule group of the recommendations panel — proposable items only, the first ten as evidence, the command the script would run for a single item, the folder to open, the rule's source. Severity by what a group frees and how safely: 1 GiB or more = review; less = good to know; never = information.
• cleanator [path] --select <rule-id> opens the app on that group, the explorer on its first item; --select <rule-id::key> also ticks that one item.

Changed

• The interface comes from bbl-ui, the crate shared by the Blackberrylabs tools. Pixel-identical — except that the interface now starts in English whatever the system language, as the other tools do; French is one click away in the footer and the choice is remembered.

Same promise: Cleanator proposes and explains; only the script you read and run removes anything.

sudo apt install ./cleanator_0.2.0-1_amd64.deb        # Debian, Ubuntu
sudo dnf install ./cleanator-0.2.0-1.x86_64.rpm       # Fedora
chmod +x Cleanator-0.2.0-x86_64.AppImage && ./Cleanator-0.2.0-x86_64.AppImage   # any distro

Cleanator 0.1.1

Cleanator 0.1.1 — lessons from the first real cleanup: a 595 GB developer home, 54.8 GiB freed in two passes, nothing lost.

Fixed

• A failing block no longer stops the script. The first real run died on sudo apt-get clean (another apt-get held the lock) and set -e skipped the remaining blocks and the final balance. Each block now runs through a small run wrapper: failures are recorded, "Free after" is always printed, failed blocks are listed, exit code is non-zero if any. apt-get waits up to 60 s for its lock.
• System directories are emptied, not removed (sudo find <path> -mindepth 1 -delete instead of a bare rm -rf without sudo on /var/crash).
• Access times are trusted only when recorded. On a noatime filesystem the last use of a model or a Python environment is unknown: shown, never proposed, no misleading date. A day that dominates the large files' access times (an indexer, a backup) is detected; items last read that day are proposed only once that day is older than the window, with the date.
• safe rules with their own dormancy window honour it (Claude Code caches younger than 7 days are left alone, as promised).
• Residues under 1 MiB (an empty trash, a 0 B journal) are no longer proposed.
• SHA256SUMS no longer lists itself.

Changed

• Language and theme are remembered between launches (~/.config/cleanator/settings.json, the only file the app writes besides the cleanup script).
• EN · FR language picker; KPI cards show a dash while scanning.

Install

• Debian / Ubuntu: sudo apt install ./cleanator_0.1.1-1_amd64.deb
• Fedora: sudo dnf install ./cleanator-0.1.1-1.x86_64.rpm (built, not yet tested on Fedora)
• Any distribution: chmod +x Cleanator-0.1.1-x86_64.AppImage && ./Cleanator-0.1.1-x86_64.AppImage

Full list in CHANGELOG.md. Found a wrong recommendation? Open an issue with the rule id.

Cleanator 0.1.0

Cleanator 0.1.0 — disk cleaner for developers who run AI on Linux. It shows where the space went (models, Python environments, Docker, package caches, AI assistants' histories), says what can go and why, and writes a shell script you read and run yourself. It never deletes anything.

Install

• Debian / Ubuntu: sudo apt install ./cleanator_0.1.0-1_amd64.deb
• Fedora: sudo dnf install ./cleanator-0.1.0-1.x86_64.rpm (built, not yet tested on Fedora)
• Any distribution: chmod +x Cleanator-0.1.0-x86_64.AppImage && ./Cleanator-0.1.0-x86_64.AppImage

Each package ships the desktop app (cleanator) and the command-line core (cleanator-cli). Checksums in SHA256SUMS.

What's inside

• 70 declarative rules, each citing the documentation it was read from — see rules/ and docs/rules.md.
• Scanner that measures like du -x; probes that ask docker, ollama, snap, journald… directly; nothing in use is ever proposed.
• Desktop app (Rust + iced): treemap, recommendations with the exact command behind each item, AI assistants and Projects views, English and French, light and dark.
• CLI for terminals and headless machines.

Full list and known limitations in CHANGELOG.md. Found a wrong recommendation? Open an issue with the rule id.