The fh- suite: sixty small commands that run the lab

Over the months, every gesture we repeated became a command. Not a platform, not a dashboard first: a short command named fh-something that does one thing, says what it did, and fails with a reason. Together they run the lab. Here they are, grouped by job.

What you get. A pattern you can copy: name your gestures, make each a small command with one job, and your agents can use the same commands you do. Most are a single file with no dependency beyond the language's standard library.

Ask and decide

• fh-ask: ask the fleet a question in plain language, answered from its sources.
• fh-assistant: one sentence to the workstation's local assistant, which points at a function (tutorial).
• fh-judge, fh-decide, fh-jev: typed decisions from the local judge (tutorial).

Hand work to agents, and follow it

• fh-dev: delegate one intention to a local coding agent; it comes back as a pull request.
• fh-task: the same through the majordomo, with its firewall and its trace.
• fh-issues: the issues waiting for an agent (tutorial).
• fh-escalade: the queue that hands a task to a hosted agent when local models could not (tutorial).
• fh-follow, fh-status, fh-inbox: a run live, the whole chain at a glance, the incidents that need you.

Know, remember, explain

• fh-kb: search the journal and the knowledge base (tutorial).
• fh-why, fh-probes, fh-history: facts for a diagnosis, and what the machine lived through (tutorial).
• fh-report, fh-kp, fh-knowledge, fh-runs-close: every run reaches the knowledge base, recurring failures become candidates for a written page, and no run disappears without a record.
• fh-tool-costs: what each tool and each skill really costs in context.

Forge and delivery

• fh-forge, fh-push, fh-relais: talk to the forge through its helper, publish a branch as a pull request, mirror the workstation's work, with no token on the workstation (tutorial).
• fh-deploy, fh-livrer: deploy one component from a closed list; deliver what is merged and roll back if unhealthy (tutorial).
• fh-backups: a copy of the hypervisor's backups, off the hypervisor (tutorial).

The machines

• fh-sante: the whole infrastructure at a glance, in about two seconds.
• fh-egpu: what PCIe link each card really got (tutorial).
• fh-alerte: a phone notification when a service fails.
• fh-kill: stop processes by pattern without killing your own shell (tutorial).
• fh-secret: a login password is born in the vault and travels by pipe, never in a file (tutorial).
• fh-mcp, fh-tools-mcp, fh-tool: the same commands and the deterministic tools, offered to any agent.

Desk and proof

• fh-pet: open the homelab cat, or say why it cannot.
• fh-fenetres, fh-apercu: one desktop window per application; publish a dev app on the private network with a clickable link.
• fh-mutant, fh-enquete, fh-bench: break the code to prove the tests, designate where to look, measure the models (tutorial).

The rule they all share

Each one says what it did, and when it cannot, says why. "Engine silent, the tunnel unit is stopped, look there" beats an empty window. A command that fails in silence teaches you nothing; one that names the cause saves the evening.

Keep a single copy of each command. Dated backups left next to the originals (fh-dev.20261002.bak) end up in tab completion and in searches; keep history in Git instead.

Found this useful? Tell us what to measure next.