Session Board 0.9.1

• The board deletes heartbeat records older than a day from %TEMP%\claude-sessions-board while it reads them. Before, one record per window start stayed behind for good and every poll in every window parsed all of them (213 files on one machine after five weeks). A record over 45 s old was and is ignored; it now also goes after a day, as does a .tmp file a dying writer left behind
• The 0.9.0 entry below names the blind marker path correctly again (a stray control character had eaten a letter)

Session Board 0.9.0

• Live sessions are grouped by VS Code window: one collapsible section per window, named after its workspace (the window's folder, or the name of a multi-root workspace), the window this board runs in first, the rest by activity; sessions started outside VS Code sit under Elsewhere. The Needs you, Working, Unseen and Idle groups are gone; inside a section the rows keep that order, and "Show N idle over 2h" folds per section
• Every section heading carries a number: the sessions in it that wait for you (amber) or are unseen (green)
• ⊘ on a row blinds the session: it moves under the folded Blinded section at the bottom and stays there, waiting or not, until ⊙ brings it back. Blinded sessions count on the Blinded heading only; the counts line, the tab title, the activity-bar badge, the toast and the browser notification leave them out. The flag lives in %LOCALAPPDATA%\SessionBoard\blinded\<id>.json, is shared by every window and the browser page, and goes once the session can no longer be resumed
• A typed filter shows blinded and archived matches in their window section, every section unfolded
• A window names its section through the heartbeat its board writes; a window still running an older board keeps the folder name until it reloads
• Browser page: POST /api/blind/<id> and POST /api/unblind/<id>

Session Board 0.8.0

• Sessions archived in Claude Code's own sidebar are put away on the board too. The board reads Claude Code's archive list from VS Code's state database (read-only, through Node's built-in SQLite) and marks those rows "archived in Claude Code"; they return when Claude Code unarchives them, and ⤒ is not offered for them
• ⤓ now also moves the transcript out of ~/.claude/projects into %LOCALAPPDATA%\SessionBoard\transcripts\<folder>\<id>.jsonl (a hard link, then the old name goes), so Claude Code's session list drops the session at its next refresh. ⤒, a click on the row or ⧉ moves it back before anything resumes it. While it is stowed, claude --resume <id> and Claude Code's own picker do not find the session; the board's search still does
• A move or a restore that fails says so on a notice line above the groups, and as a VS Code warning; the session stays archived on the board
• ✕ is unchanged: Claude Code keeps an ended session in its list until its own auto-archive (claudeCode.archiveInactiveSessions, 14 days by default; sessions that are open, waiting or unread are never auto-archived)
• The browser page needs Node 22.13 or newer for the state-database read

Session Board 0.7.0

• New group Unseen between Working and Idle: a session whose answer ended while the board was running and that you have not opened since. Its row says "unseen" with a green mark; opening it from the board, or sending it a new prompt, moves it back to Idle. Sessions that were already idle when the board started are not flagged
• ✎ on a row asks for a new title from the session's progress: one short haiku call over the recent prompts and the last answer, hook-free and without tools. The title is the board's own; Claude Code's files are not written, and a later /rename wins again

Session Board 0.6.1

• The Marketplace page shows its screenshot again; the image link pointed one folder too high

Session Board 0.6.0

• The usage strip now names the account the claude command is signed in with: the email, with organisation and plan on hover. It comes from claude auth status --json, run beside the usage probe. A logged-out CLI shows "not logged in"; a CLI without that command shows no account and the Output channel says why
• The Marketplace page shows its screenshot again; the image link pointed one folder too high