A small fleet of agents, run from a ring on your finger.

Dispatch is my personal agent-ops stack. I speak a task into a ring on my finger and a running agent answers in a Telegram thread, usually in minutes.

What it removes is the cost of starting. Most things I put off die at the moment of intention, when doing them means finding a laptop, opening a session, writing the prompt. If starting a task costs one spoken sentence, nothing gets deferred. Put everything on and take off. The stack exists to make the distance between wanting something done and it being done about one breath long.

The loop stays small. The ring transcribes. A dispatcher reads the intent against a closed list of capabilities, and low confidence fails closed. Anything dangerous waits behind an approval button in the iOS app, where a misheard syllable cannot open a gate. Around the loop, a provisioning service gives an invited person a private VM with an agent runtime and its own Telegram bot. A swarm runner keeps an append-only ledger of runs on disposable cells.

The failure modes taught me where the gates go. A webhook and a DM disagreed about which session a reply belonged to, so replies now get injected into the live session itself. The approval gate shipped fail-open and an 11-finding security audit flipped it; every finding got a regression test. A stubbed audit showed a lease expiry could provision the same VM twice, so the resume path has tests proving exactly one gets created.

It has been my front door since late August, running on rented VMs and a Mac mini, with the provisioning side serving invited users at lunchbox.exe.xyz. The delegate protocol itself is public at github.com/il-figlio/index01. The limit worth naming: it works because the closed capability list is mine. Turning it into a product means someone else decides what an agent may do, and that decision is the whole company.