sz-chrome-remote-extension.git/test-suite/unit/shared-window.test.mjs, branch masterpi-chrome, patched to drive a signed-in browser on another host through a broker, with an MCP server
https://git.soarez.net/sz/sz-chrome-remote-extension.git/atom?h=master2026-11-08T17:11:15+00:00tabs: back to one window per session; keep new tabs out of the user's window2026-11-08T17:11:15+00:00Igor Soarezigor@soarez.org2026-11-08T17:11:15+00:00urn:sha1:b8b63ea4d1bad9c4bbac6b05b03cce5f2cfa3f94
A window shows only one tab, so sessions sharing one hid each other's tabs: no
real input and blank screenshots for every session but the one whose tab was
active (castle-pirc-web, 2026-11-08). Time-sharing the active tab would flip tabs
under the user while they sign in for an agent, so revert 66fbd30: a session
gets its own unfocused window. Kept: chrome_tab new for a session with no window
opens one for it instead of landing in the user's focused window. The primer
and chrome_tab description now say why to reuse a tab.
tabs: agent sessions share one window instead of opening one each2026-11-08T12:37:44+00:00Igor Soarezigor@soarez.org2026-11-08T12:37:44+00:00urn:sha1:66fbd3015ff68aa94f1faff1ad84740052b86a0d
A session's first tab used chrome.windows.create, so every new session name (and
every Claude Code process) got its own window. It now goes into the window that
already holds any 'Pi Session:' group; a window is created only when none exists.
chrome_tab new for a session with no group also uses that window, not the user's
focused one. The primer and the chrome_tab description say so.