Working with it
Clicking a row
One click gets you into that window, marks what you saw, and never takes focus on the way.
Click a lamp and the editor window hosting that session comes to the front. One click is enough even when you are working somewhere else: the panel makes itself key just before the click is dispatched, so the first click is delivered rather than spent on focus. A double click counts as one, and the second is dropped.
The panel itself never takes focus. It is a non-activating window, which is why clicking a lamp does not flicker your editor away and back.
What the click also does
It marks the row as seen. Amber, green and red all return to rest, the grey ring, because all three are states where the news has now been read. Yellow and blue do not clear, because there was nothing to read in the first place.
On a sample row the click reads the sample instead, since there is no window behind it.
On a grouped row it clears only the sessions that were in the most urgent state. One row per project explains why.
The modifiers
| click | raise the window, mark as seen |
| ⌘ click | open the Hub on that session |
| ⌥ click | raise the window without marking anything as seen |
| ⇧ click | open a Finder window in that project's folder |
The row's menu says the rest in words, for when you would rather not remember them: Open in the Hub is ⌘ click, and under More, Open without marking as read is ⌥ click and Show in Finder is ⇧ click.
Where a click lands
| The session runs in | The click raises |
|---|---|
| VS Code, Cursor and other forks | that window, and optionally the agent's tab inside it |
| a terminal | the tab hosting the session, found through the session's process |
| the Claude desktop app | the app |
| another machine over ssh | the Remote-SSH window for that folder, if one is open here |
the background, started with claude --bg, or tmux | the Hub, where its terminal is, when A click opens the session in the Hub is on in Settings › Clicks & keys |
VS Code exposes no AppleScript dictionary, so the only handle is the window title. The app scores the titles it reads and raises the winner. It matches by title and not by index, because reading the titles and raising a window are two separate events, and between the two the window order changes on its own.
The tab, not just the window
Once the right window is in front, the click can also open the agent's tab for that precise session, through a URI the extension registers.
This is off by default, for two reasons. It is an extension's internal contract rather than a public API, and VS Code asks for confirmation on every invocation. The switch is Also open the conversation's tab in VS Code, in Settings › Clicks & keys, so if a future version changes the contract you can turn it off without recompiling. If it stops working the click still takes you to the right window.
When the click cannot do its job
The panel says so on itself: a line appears under the rows with a button that explains the missing permission and opens the right pane in System Settings.
It used to say so only at the bottom of a context menu, which is a place nobody looks, and the result was an app that read as broken. See what it asks for.