Skip to content

docs: call out the dormant extension service worker after a late install #276

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
lianghua1 wants to merge 1 commit into
base: main
Choose a base branch
from
+9 −0
Open

docs: call out the dormant extension service worker after a late install #276

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions AGENT_INSTALL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.<date>` 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`.
Expand Down