I run several coding agents at once. Not because it is fast, but because queueing work behind one agent means I am the bottleneck.
The failure mode is not a crash. It is silence.
agent A: refactoring the parser (fine)
agent B: waiting for a decision (has been, for 40 minutes)
agent C: rewritten the same file as A (nobody noticed)
agent D: done, reported nothing (nothing to report?)
Four terminals and not one of them tells you which is blocked. You find out when you switch windows.
What I tried first
A notes file. It works until two agents append at the same time and one write wins. Then a database: now the log outlives the machine, needs a server, and the whole point was that this stuff should still be readable next year.
What I built instead
One append-only Markdown file, one lock, one writer process:
- every agent writes with a handle:
node chat.js send --as agent-b "tests pass, 12/12" - the file is plain text, fenced, and a parser is the only thing that defines "a message"
- a tiny relay serves a live board over Server-Sent Events, so the board updates as agents write
- questions are first class:
ask:thendone:with an id, so "who is waiting on whom" is a grep, not a memory
No account, no cloud, no daemon you have to keep alive somewhere.
Three bugs worth knowing about if you build this
1. The lock path must be derived from the log path. Mine was derived from the project root, so pointing CHAT_PATH elsewhere gave two writers two locks and four of ten messages vanished. No error, no warning.
2. Windows refuses to rename over an open file. EPERM on atomic replace is not corruption, it is contention. Treat EEXIST, EPERM, EACCES and EBUSY the same way or your writer dies at random.
3. .slice() splits emoji. Truncating a message at 400 UTF-16 units produced invalid text. Slice code points, not units.
The part I did not expect
Tests are what made it usable. A shared log is a concurrency problem wearing a text file costume: fence injection, header parsing, empty-lock races, two clients on one relay. There are 344 tests here, and most of them exist because something I was certain about turned out to be false.
It is a product now
The log, the CLI and your history are free, and they stay free. What a licence buys is the live board — the panel that tells you which agent is blocked — after the thirty-day trial, plus a year of updates and a re-issue if you lose your key.
The key itself is signed with Ed25519 and verified offline, so it works on a plane, and there is no account to create. Bitcoin only for now, because that was the fastest way to take money without a company; card payments are being added.
Trial and details: https://agentlog-3ey03c.freebuff.site/?ref=devto
If you run more than one agent, I would like to know what your version of "agent B is stuck" looks like.
Top comments (0)