sz-chrome-remote-extension.git/extensions/chrome-profile-bridge/browser-extension, branch master

tabs: back to one window per session; keep new tabs out of the user's window

2026-11-08T17:11:15+00:00

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.

overlay.clear: read closed shadow roots and remove the host element

2026-11-08T16:31:10+00:00

Diagnostics on 1Password's inline prompt: the page holds a element and no iframe in its own DOM; the frame is inside a closed shadow root. Run in the isolated world, where chrome.dom.openOrClosedShadowRoot can read it, and remove the element that hosts a foreign extension frame. Drop the body-click events: they were never shown to help.

overlay.clear: match the prompt's frame by the tabId in its URL, and report what it saw

2026-11-08T16:17:05+00:00

The password manager's frame target can come without a tabId, so it was missed (error said 'unknown', remaining targets empty). Match by the ?tabId= in the frame URL too, and when the tab stays blocked report every foreign target and what the injected script saw, so the next step is based on data.

overlay.clear: run in the page's own world with the click the fallback uses

2026-11-08T16:10:10+00:00

The isolated-world body events did not free a 1Password-blocked tab; the DOM click fallback (MAIN world, full pointer event shape, el.click()) did. Use that shape, aimed at the page root so no control is clicked.

overlay.clear: click the page body outside the prompt, and wait for it to go

2026-11-08T15:32:11+00:00

Measured on 1Password's inline menu: blur and Escape did not free the tab, a click outside did. overlay.clear now also sends pointer/mouse events to the body and polls the debugger for about a second instead of checking once.

overlay: the agent decides whether a password-manager prompt is in the way

2026-11-08T15:26:17+00:00

The error, the tool description and the primer no longer tell the agent to ask the user first. It clears the prompt when it is only in the way, and leaves it alone and says so when it is waiting for the user to sign in or approve.

overlay: tell the agent about a blocking password-manager prompt; chrome_clear_overlay closes it on request

2026-11-08T15:19:35+00:00

Another extension's frame (1Password's inline prompt) makes Chrome refuse the debugger on the tab. The old path sent Escape on its own, which cannot reach that frame and would close a prompt the user may be using. Now nothing is closed automatically: the error says what is blocking and tells the agent to ask the user; chrome_clear_overlay removes the frame, blurs the field, sends Escape and reports whether the tab is usable again.

navigate: do not require the debugger

2026-11-08T15:10:48+00:00

Attaching first (for the Leave-site prompt) made chrome_navigate fail on a tab whose page holds another extension's frame, such as a 1Password inline prompt, which is exactly when navigating away is the way out. Attach is now best effort.

tabs: agent sessions share one window instead of opening one each

2026-11-08T12:37:44+00:00

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.

navigate: answer a page's Leave-site prompt instead of hanging

2026-11-08T11:58:33+00:00

A page with a beforeunload handler shows 'Leave site?' when the extension navigates away. Nothing answered it, so chrome_navigate waited out its timeout and the agent never learned why. The worker now hears Page.javascriptDialogOpening and dismisses the dialog (stay/cancel); page.navigate fails at once and says so. leaveIfAsked: true, for that call only, accepts a beforeunload prompt. Tool description and primer tell agents when to use it and to ask the user when unsure.