Telling Technology · Learning in public
All episodes
EP.70 — LIVE JUMP
A Claude Code workflow, on screen

Click a link, and the terminal jumps to life

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.

A live-sessions page where each running Claude Code session is a jump-link, next to a VS Code window raising itself to the front
⎍ one URI · cross-window · ~0 ms of searching
It started with the same question every twenty minutes: which tab was that in?
01 The tab hunt

Parallel sessions are great until you have to find one

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.

claude code — desktop
> I have ~12 Claude sessions running across VS Code windows. I want a link I can click that focuses the terminal tab running a specific session id. Is that even reachable from an extension?
Yes — two halves. VS Code can register a URI handler (vscode://<publisher>.<ext>/...), and the terminal API exposes each terminal’s shell processId. The gap is that your session id is not the shell PID: Claude runs inside that shell. So the match has to walk the process tree, not compare two numbers.
Four VS Code windows with dozens of unlabelled terminal tabs, one of them holding the wanted session
which tab?
Twelve live sessions, zero labels. The retrieval problem, drawn.
02 The build

A session map, a URI handler, and one walk up the process tree

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 code — desktop
> Build the extension. Resolve the session id via ~/.claude/session-map.json, then match the recorded PID against the terminals in this window by ancestry.
Done. One Get-CimInstance Win32_Process call builds a full pid→parent table, so the ancestor walk is pure in-memory lookup — no per-terminal shelling out. Extension activates on onUri and onStartupFinished; the debug trail lands in ~/.claude/aios-jump.log.
Diagram: statusline writes session-map.json, extension reads the PID and walks the ancestor chain to a terminal shell PID
statusline → map → PID chain
The session id is not the shell PID. Ancestry is the join key.
03 The honest part

The first version only worked if you were already in the right window

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 code — desktop
> Clicking from window B does nothing when the session lives in window A. What is the cheapest cross-window path that does not need a server?
A watched file. Write the request to ~/.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.
A click in one VS Code window while a different window raises itself to the front with the matching terminal tab focused
wrong window → silence
The bug was invisible: it worked whenever you did not need it.
⚠️

Sideloaded means you have to reload

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.

04 What it looks like

Four screens from a two-hour build

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.

BUILT AND RUNNING ON THIS MACHINE

The dashboard can now reach into a session that is still alive

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 live-sessions page open beside a VS Code window that has just raised itself with the matching terminal focused
one sideloaded extension · one CIM call · one watched file · no server
06 Steal this

Steal the jump link

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.

skill aios-jump — VS Code URI handler + PID ancestor match cmd /sessions — global command that opens the live page template live_sessions_page.py — session map to HTML assets statusline hook that writes session-map.json
run it 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.

Next episode

Next: I made the show itself readable by machines

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.

An llms.txt file listing every episode of the show
drops soon · follow so you don’t miss it