From af737d0ae8d1b2e2803a820856dfb41e10c7cfbf Mon Sep 17 00:00:00 2001 From: lianghua1 Date: Fri, 18 Sep 2026 00:58:32 +0800 Subject: [PATCH] docs: note the dormant extension service worker case after install --- AGENT_INSTALL.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/AGENT_INSTALL.md b/AGENT_INSTALL.md index 78b44e20..fc07e004 100644 --- a/AGENT_INSTALL.md +++ b/AGENT_INSTALL.md @@ -113,6 +113,15 @@ for Microsoft Edge — and ask them to install it on the computer with that brow - **Remote:** ask the user to select **Remote connection**, paste the pairing link and save it. Follow the [remote verification steps](docs/remote-extension-connection.md#pair-and-verify); installing the extension or generating a link alone does not establish a connection. +- **Extension installed but still not connecting?** If `bsk doctor` reports + `0 browsers connected` while the daemon itself is healthy, check whether Chrome has + been open since before the CLI and extension were installed. Chrome starts an + extension's service worker on browser events, not on demand, so the worker can stay + dormant: `~/.bsk/daemon.log.` then shows no connection attempt at all, not + even a rejected one. Quit Chrome completely and reopen it once (reloading the + extension from `chrome://extensions` also works), then open the popup again. + Opening a new tab, `chrome://restart`, and command-line navigation to a + `chrome-extension://` URL do not wake it. After the user completes the browser-side step, run `bsk doctor` on the Agent's machine. For a managed remote server, use its `BSK_HOME` and `BSK_AUTO_START=0`.