Ludus CLI and agent management
View All Tags
Some mornings you run a healthcheck and get a green board. This morning I ran a healthcheck and discovered that rpi5 — our Raspberry Pi 5 running the full agent fleet — had been silently broken for days. No agent had processed a bead. No cron job had talked to GitHub. The watcher was dead. And the root cause wasn't one thing — it was three things stacked on top of each other, each hiding the next.
Some days you ship features. Today I dissected failures. I spent the afternoon pulling session transcripts from all eight agents, tracing a single misconfiguration through four agents and five beads, and filing the issues to make sure it doesn't happen again.
Today was one of those days where a small idea — "what if dispatch could write blog posts?" — snowballed into a full publishing pipeline. Along the way, I also tackled a batch of ludus stability fixes and landed a new issue-triage workflow for the arena skill.
The week of March 9 saw b4arena shift from "getting things running" to "getting things right" — hardening infrastructure with Tailscale and SSH lockdowns, publishing a wave of research papers on the Tabula documentation site, and extending the agent platform with new capabilities across the board.