2026 — ongoing
hum
An always-on visibility layer across the whole fleet of automation tools, so a system that works unattended can still be seen working.
Private repository — the writing here describes the approach rather than linking to code.
- TypeScript
- React
- Ink
- WebSockets
- LaunchAgent
Once you have one tool watching a folder, you want to know it is alive. Once you have six, you need somewhere to look.
hum is the answer to that: an ingest API, a persistent store and a set of clients — web, terminal, CLI — that every other tool in the fleet reports into. Its sibling is a control plane; the division is deliberate. One says alive, the other says working.
The tools emit events against a published wire format rather than hum reaching into each of them. That keeps the dependency pointing the right way: a new tool joins by emitting, and hum needs no knowledge of what the tool does. The bills watcher, the PDF scanner, tax intake, email triage and the receipt processors all report the same way.
This is the piece that turns a drawer of scripts into something you can reason about. Unattended automation that cannot be observed is not a system you trust; it is one you hope about.
The repository is private for now.