len5ky / sessiondeck

# SessionDeck
SessionDeck tracks the Claude Code, Codex, GitHub Copilot and Cursor agent sessions running on your machine in one sidebar tree, grouped by project, with a status icon on each row. A red bell shows which Claude Code session is waiting on you. Click the row and you land in its tab or terminal; for a Claude Code session that works from another window too.
If you searched for a way to track Claude Code or Codex agent sessions across VS Code or Cursor windows, this is that.
Status is inferred from transcripts and process state on disk, not reported by the agents themselves, so it can lag or misread an edge case. The rest of this page says where.
It's for people who run many agents at once and lose track of which one stopped to ask.
## Install
**VS Code** (Visual Studio Marketplace):
 [code] 
Or search **SessionDeck** in the Extensions view.
**Cursor** (Open VSX): search **SessionDeck** in the Extensions panel, or run `cursor --install-extension len5ky.sessiondeck`. If Cursor can't find it, download `sessiondeck- .vsix` from GitHub Releases and run **Extensions: Install from VSIX...**.
**Remote windows** (WSL, Remote-SSH, dev containers): SessionDeck runs on the workspace side, so it goes into the remote, next to your sessions. The optional bridge for seeing several hosts in one tree goes on your **local desktop** instead, and installing SessionDeck from the Extensions view puts it there for you; see Other hosts.
### Platform support
- **Linux and WSL**: full support; this is what it's built and tested on.
- **macOS**: works, minus the `/proc` features. Auto-detected config homes degrade, and discovery is limited to config homes it already knows about. Terminal matching, the ↗ badge and Move into Editor read the process table with `ps`.
- **Native Windows**: the tree works on the 3-second poll, without hooks or approval alerts. Install Hooks isn't offered there, and running it from the palette writes a POSIX shell script SessionDeck doesn't support on Windows. Terminal matching, the ↗ badge and Move into Editor read the process table through PowerShell, so a new session can take a few seconds to get its badge.
**Run Diagnostics** reports what works on your machine. Trust it over this list.
### First run
1. Click the compass icon in the activity bar. That's the SessionDeck view; your sessions appear under **Sessions**, grouped by project.
2. Run **SessionDeck: Install Hooks (instant updates + approval alerts)** from the command palette. Without hooks the tree still updates on a 3-second poll, but it can't see a session stuck on a permission prompt: that session just looks like it's working. Hooks are written into each Claude config home on the machine where SessionDeck runs, so do this once per machine (once per remote host, too). They apply to sessions started afterwards.
3. If the tree is emptier than you expect, run **SessionDeck: Run Diagnostics**. It prints one line per subsystem and the fix for each problem, and changes nothing.
##