CodeKanban

Putting terminals and coding agents onto a kanban board is a small reframing with an outsized effect on how manageable parallel work feels. Instead of hunting through tabs you see state at a glance and drag work through stages, and in practice that made supervising several agents far less stressful. The open questions are about persistence across restarts and how it represents an agent that has silently stalled, since a card that looks done but is not is worse than no card. With clearer liveness indicators it would be a tool I keep open all day.

Treating my terminals and agents as cards on a board turned a chaotic pile of windows into something I can actually plan around. Moving a task between columns and watching its agent pick up was satisfying. Keyboard control for the board would seal it.

A board that gathers every terminal and agent in one place is convenient, and I want it to be equally good at showing me what each one is permitted to do. The overview was clear and current. A per-task record of commands run would let me trust it with more.