An experimental, repo-local coordination layer for coding agents: folders are columns, Markdown files are tickets, and Git is the audit log.
Status: experimental. I started Agent Board last night. The protocol will probably change.
There is a point with agent orchestration software where you stop feeling like you are shipping software and start feeling like you are operating an airport.
Planner. Supervisor. Queue. Registry. Worker pool. Dashboard. Trace viewer. Retry policy. Task graph.
Somewhere in that pile, an agent writes useful code.
I kept ending up with the same questions:
Agent orchestration works better when loops, retries, fanout, and approvals move from prompts into executable code with a narrow…
The short version Agent framework Agent runtime Operates during the days you write...
A single agent — one model, a system prompt, a handful of tools, and a loop — gets you surprisingly...
Coding agents are very good at finishing bounded tasks. They are not, by themselves, good stewards...
A queue of plain markdown files coordinating humans and machine agents, with acceptance tests and evidence-or-it-is-not-done.
Here's a workflow that has quietly become normal in 2026: you open a terminal, type claude (or fire...
