One page that shows why each AI coding session exists, how far it got, and whether it can be closed.
live
Next.js · React · TypeScript · SQLite · Tailwind
oct 23 → oct 27
Board of coding sessions grouped by what each needs next, with verdicts and pull request counts.
Customer
Builders running many AI coding agents in parallel, often 20 or more sessions at once, many of them days or weeks old.
Problem
Coming back to an old session means rereading the whole conversation to learn why it exists and what's left. That costs enough that people put it off, and the pile of half-finished work keeps growing.
Outcome & measures
A page on desktop and phone that lists every session with its purpose, progress, open pull requests and a suggested verdict, so each one can be closed, parked or resumed at a glance.
Closing a session goes from rereading everything to glance and decide
Work the pile down in 10-minute sittings, mostly from my phone
Nothing merged or deleted unless I clicked that exact item
What's next · Dec 2026
A small test of replying to a session straight from the board, before deciding whether to build it.
Why I built it
Running many agent sessions at once is great until you return to them. The built-in view showed state, but never the why or what was left.
How it came together
Version one summarized every session. Run against my real sessions, it found about 180 open items and nothing ready to close: it made the pile look bigger. Version two added a verdict per session and a one-at-a-time triage mode.
What I learned
A dashboard that only describes the problem can make it worse. The useful step was having the board suggest a decision, with evidence, and letting me accept or overrule it.
