pickfit

BrowseDeveloper CLIs

storage_ballast_helper

Daemon that monitors disk pressure and safely reclaims space for AI coding workloads.

Tested on Linux

Use it

Linux x86_64

  1. Download installer script for reading

    curl -fsSL https://raw.githubusercontent.com/Dicklesworthstone/storage_ballast_helper/main/scripts/install.sh -o /tmp/install_sbh.sh
  2. Run installer script user install

    bash /tmp/install_sbh.sh && ~/.local/bin/sbh --version
Where the README and reality differ
  • README: ./target/release/sbh --help
    What worked: sbh is at ~/.local/bin/sbh; used sbh --help and sbh status/check/scan/ballast/emergency

Check that it works

sbh --help

The output should contain “Show current health and pressure status”.

First thing to try

sbh status --json

Run sbh status --json to see the current disk pressure and ballast pool state.

What it does

  • Monitor disk pressure and predict when it fills
    How to use it
    1. Run sbh status --json to see overall pressure, ballast pool health and daemon state.
    Tested
  • Free space by cleaning up build artifacts
    Not shown working
  • Release ballast pools on several volumes
    Not shown working
  • Recover a full disk in zero-write emergency mode
    Not shown working

How far pickfit got

Linux x86_64

  1. Installs
  2. Starts
  3. 1 of 4 features work
  4. Works offline

macOS: the project says it runs there; pickfit hasn’t tried it.

Good for

  • provision per-volume ballast pools
  • protect critical projects from cleanup
  • scan projects for cleanup candidates
  • execute safe cleanup to target free space
  • recover critically full disk in emergency mode

An alternative to Cron + rm scripts, Generic temp cleaners and Manual cleanup.

How pickfit tested it

Each run starts from a clean machine and follows the steps above. How pickfit verifies

Linux x86_64

Its main function works

  • Replayed from scratch
  • Works offline
  • Checked on 30 Oct 2026
  • Version 0.7.9

Differences the test machine hit

  • README: curl -fsSL .../install.sh | bash
    In the test: downloaded to /tmp/install_sbh.sh, read it, then ran bash /tmp/install_sbh.sh
  • README: sbh emergency /data --target-free 10 --yes
    In the test: sbh emergency has no --dry-run; used sbh emergency /tmp/sbh-test --target-free 1 --yes which exits 0 with nothing to reclaim

How to read a tool card

Stitching
pickfit installed this tool itself. Everything under the stitches comes from that run. A tool pickfit has not run never gets stitches.
Verified on your OS
The install steps ran on the system you chose. “Ran on Linux only” means it has not been run on yours yet.
macOS, Linux and WindowsWhere it ran
Green OS marks: pickfit ran the install steps there. Grey ones: the README says it runs there, and pickfit has not tried.
How far the run got
Installs and starts, its main function works, its service answers, it produces model output. A window means a desktop app opened; a plug, an MCP client used it. The mark sits beside the run’s result, under “Why it fits and how we know” and in “How pickfit tested it”.
Visual check
pickfit looked at screenshots of the app. Green: it looks right. Amber with a number: things that look wrong; open it to see them. Grey and dashed: not checked yet.
Known vulnerabilities
Known high or critical vulnerabilities (OSV.dev) in what it installs. Green: none known. Red with a number: how many; open it for the list, and read it before you install. Grey and dashed: not checked, which does not mean safe.
About the run
The day it ran, and the version that ran.
Source of a reason
Every reason a pick fits rests on one profile field. Open the reason to see the field and the value it relies on.
Hidden gem
High quality, little known.
Quality and popularity
Two scores out of 100. Quality: how well it installed and worked when pickfit tried it, and how good its install docs and upkeep are. Popularity: from stars, downloads and Hacker News.
Features checked
Of the main features the README advertises, how many the run actually exercised (green), and how many failed (red). Grey ones were not checked, and the card says why.
Not verified
A well-known tool Fitz mentions from general knowledge. No run record, no steps, no score.