#developer-tools

Sources: my private workspace records for that day (the mission’s spec, progress log, slice proofs and review verdicts), and the merged PRs in my public skills repo. Times are UTC.

I run a fleet of coding agents: several teams of them, on three machines, each team working through one project. For months the process lived in prose. My root AGENTS.md was 4,496 words. Reviews passed because a reviewer agent said “looks good”, and nobody could tell which diff it had looked at.

On Sunday 8 November I wrote seven decisions down and handed them to the fleet. By the next morning the agents had built most of the gates that enforce them, and the gates had already caught real mistakes, including some in the gates.

Read More

Sources: the rexboard repo (README, docs, ADRs and the CHANGELOG up to v0.20.0), my own mission notes for the build, and the tools I compared it with: Fleet, Agent Deck, cc-pane, Muxbell and Mux Beacon.

On a normal day I have somewhere around 70 agent panes open across three machines. Most of them are fine. A few are stuck on a permission prompt, one has finished and is waiting for me, and one hit an error twenty minutes ago and I have no idea which. I kept losing time hunting for those panes, so I built a board that finds them for me.

That board is rexboard. It went from v0.1.0 to v0.20.0 in about a week. This post covers what it is, why it works the way it does, where it stands, and what I want to add next.

Read More

Your browser is out-of-date!

Update your browser to view this website correctly. Update my browser now

×