agent infrastructure
durable sessions, orchestration, and review for coding agents.
agents do their best work when the environment around them is boring: durable sessions that survive a closed laptop, one writer per machine, commands recorded before they run, and a human who can review before anything lands.
four of these lessons come from oompa, the cli and daemon hraness ran its codex, claude code, and devin sessions through until xcb superseded it on september 19, 2026. they cover session leases, command records, isolated provider accounts, and live control, and the cases where each one breaks. the lesson on verification loops comes from direct.
lessons
- one writer per session: leases and fencing for durable agent sessionsstart here · how a durable agent session stays consistent when the laptop closes
- idempotent command records: the audit log an agent runtime owes yousubscriber · record the mutation before you dispatch it
- isolated provider accounts: why agent capacity means n subscriptions, not one api key · clean handoffs between accounts without losing the thread
- deterministic verification loops an agent can trust · repeatable states instead of staging environments
- steer, queue, or redirect: three semantics for live agent control · intervening in a running agent without forking it
projects
- oompa · the retired session runtime these lessons describe; xcb superseded it.
- ghostget · typed website capabilities for agents.
- direct · repeatable app states for frontend testing.
by hraness · drafted with ai assistance