The problem
The session board is the part of my desktop shell that shows every running Claude Code session as a card.
How it works
Past four or five sessions, terminal tabs stop being manageable. You lose track of which one is running a long job, which one finished, and which one has been waiting for your answer for twenty minutes. Here each session gets a card with its name, its current step, and its state: working, waiting for me, or done.
Cards group automatically by project and by life area, so a work session and a personal one never sit in the same group by accident. I can also drag cards into my own groups. When a session closes it moves to a history, where I can search it and reopen it if I need to.
- Every session as a card with state
- Groups form automatically by project
- History keeps closed sessions findable
Outcome
My day runs through it. The "waiting for me" state exists because the expensive part of running many agents is not compute; it is the human they are blocked on.
Stack
- claude-code
- windows
- webview2
- desktop-shell
- developer-tools
Code
github.com/HenryLop/session-board
Transcript
Twelve AI sessions open at once, all on one board. The session board shows each one as a card: its name, what it is doing, and whether it is waiting for me. Sessions group themselves by project and life area, so work and personal never blur. Closed sessions move to a history I can search and reopen. It turned a pile of terminal windows into something I can actually run.
How this was made
Voiceover is text-to-speech (Microsoft Edge neural voice). Background art is AI-generated (Gemini). Titles and captions are set in code, not generated. The build itself was made with Claude Code.