One page for every Claude Code session

I run a lot of Claude Code sessions at once. On one build this month, 25 of them were active in a single day. So I stopped clicking through them to find the one that needed me. One session is the manager now, and it keeps a single page, the Session Board, with every question from every session and a reply ready to copy. It's a free Claude Code skill on GitHub, there's a step-by-step setup guide, and the video below shows it working.

Skill: github.com/justfinethanku/lej-claude-session-board (MIT)
Setup: Guided setup, four short tasks
You need: The Claude desktop app, with its Code tab
Made with: Claude Code

What it does

Three minutes, start to finish: installing it, making a manager, reading the board, answering, and starting new work. The project in the video is made up.

The LEJ Session Board · 2:57

Why I built it

I build with a lot of sessions going at once. Each one takes a piece of the work: a feature, a fix, a data job, a deploy. That's the fast way to build right now, until they all start waiting on you.

A session that's waiting on a decision doesn't tell anyone. It just sits there. With ten or more open at once, I was clicking through them one at a time to find the ones that needed me, and while I did that, the rest sat too. I'd become the switchboard, and I was the slowest part of the whole system.

Every question had to find me before any work could move.

So on September 29th I made one session the manager. Every other session reports to it, and it keeps one page current. That night the board was relaying for about ten sessions working at once, and I answered them from one page instead of ten tabs.

How it works

Manager
One session in your project folder. It takes the roster, sorts your sessions into stale, in progress and needs follow-up, and writes a short rule into the folder's CLAUDE.md so every session reports to it.
Reports
Every session sends the manager a short update when it starts something, when it needs you, before a deploy, and when it's done.
Board
One private page with a section per session: what it's doing, where it stands, and its questions for you. The manager's own questions sit at the top.
Answers
Every question has two or three options, one marked Recommended, and a reply you can edit. Copy puts the session's name and the question on top, so you can paste a batch into the manager and it sends each one where it goes.
Deploys
A yes passed along by the manager lets a session build, not ship. For a production deploy, you type go in that session yourself.
New work
The to-do list is grouped by who acts. Anything Claude can build has a numbered starter prompt, title included, ready to paste into a new session.

What you need

The Claude desktop app. The board runs in its Code tab, because it uses the app's session tools to read your other sessions and message them. The terminal version of Claude Code doesn't have those tools.
A project folder where you run more than a couple of sessions. The manager looks after every session in that folder and the folders inside it.
git, to download the skill. Macs ask to install it the first time you use it.

Set it up

The setup guide walks through four short tasks: install the skill, make a manager, answer from the board, and start new work. Each one stands on its own, and your progress stays in your browser.

Open the setup guide

Or, in Terminal:

git clone https://github.com/justfinethanku/lej-claude-session-board.git ~/.claude/skills/lej-session-board

Then, in a Code tab session in your project folder, say: