Blog
Notes on building Murongi
Short pieces on why I built Murongi and how it keeps work moving.
-
Why I built an orchestrator
I run AI agents across several machines for my own work, and the work kept stalling when I stepped away, so I built Murongi to keep it moving.
-
Guardrails that keep work moving
A guardrail that only halts work makes more work for me, so each of mine tries to send a task somewhere useful before it gives up on it.
-
Measuring before trusting
Why I count each agent run, how a usage meter and cost alarms feed the Limited guardrail, and what I changed after the numbers surprised me.