I run a dozen Claude Code sessions at once, spread across VS Code windows I lost track of hours ago. Now one click resolves straight to the right terminal tab — even if it lives in a window that is behind everything else.
Running work in parallel is the whole point of an agent setup: one session drafting an episode, one chewing through a migration, one babysitting a nightly build. The cost nobody mentions is retrieval. Four VS Code windows, thirty-odd terminal tabs, and no label anywhere that says which one is holding the thread you actually want. So you alt-tab, squint at scrollback, guess wrong, and do it again. The sessions were never the bottleneck — finding them was.
Half of it already existed. My custom statusline writes ~/.claude/session-map.json on every turn — session id, the Claude process PID, the cwd, the last prompt. That file is the index. The new piece is aios-jump, a sideloaded VS Code extension that handles vscode://jacob.aios-jump/focus?session=<id>. On a click it looks the id up in the map, takes the PID, and asks Windows for every process’ parent in one CIM call. Then it climbs from each terminal’s shell PID and checks whether the session’s PID is a descendant. First hit wins: that terminal gets shown.
~/.claude/aios-jump.log.
An extension host is scoped to its own window. It can enumerate that window’s terminals and nothing else — so the first build focused the tab perfectly when the correct window happened to be in front, and silently did nothing when it was not. Which is the exact case the whole thing existed to solve. The fix is a dead-simple relay: if no local terminal matches, drop the request as ~/.claude/aios-jump-request.json. Every window watches that file. The one that owns the session picks it up, self-raises via code <folder>, and shows its own tab. And when the id resolves to nothing at all — session ended, machine rebooted — you get a toast with a copyable claude --resume <id> instead of a click that does nothing.
~/.claude/aios-jump-request.json; every window’s handler polls it, and only the owner acts — it raises itself and focuses the tab. No port, no daemon, no IPC to keep alive. The failure mode is a stale JSON file, which is a rounding error next to a background service.
Installing the .vsix does not activate the extension in windows that are already open — they keep running the stale extension host. My first “it’s broken” round of debugging was three windows that had simply never loaded the thing. Reload every open window after an install, or you will debug your own memory of the code.
The session map, the jump-link page, the cross-window relay, and the failure that is not a dead end. Tap any image to enlarge it and read the exact prompt that drew it.




scripts/live_sessions_page.py renders the session map as inbox/live-sessions.html: every session currently running, each title a jump-link. A new global /sessions command opens it from any project. The dashboard already read my finished conversations — transcripts, dead, archived. This is the first time it reaches into one that is still thinking and puts it on the screen.
The full build on screen: the session map, the URI handler, the ancestor walk, and the cross-window relay that makes a click in one window raise another.
The extension, the statusline hook that writes the session map, and the page generator that turns it into clickable links. Everything in this episode is free and open — clone it, run it, make it yours.
repo not published yet — the extension is walked through line by line in the video
No GitHub? Comment JUMP on the post and the bot DMs you the link.
A sitemap, an AI-crawler allowlist, per-episode JSON-LD, and an llms.txt that had quietly gone fourteen episodes stale. If agents are the new audience, the site has to be legible to them too.