[Bug]: opencli-extension-v1.0.12.zip works well with 1.7.19, but opencli-extension-v1.0.15.zip do not work with 1.7.21

[zhudy]

Description

opencli-extension-v1.0.12.zip show: Connected to daemon, while opencli-extension-v1.0.15.zip show: Checking... there is warning: Service worker registration failed. Status code: 2
{
"manifest_version": 3,
"name": "OpenCLI",
"version": "1.0.15",
"description": "Browser automation bridge for the OpenCLI CLI tool. Executes commands in Chrome tab leases via a local daemon.",
"permissions": [
"debugger",
"tabs",
"cookies",
"activeTab",
"alarms",
"storage",
"tabGroups",
"downloads"
],
"host_permissions": [
"<all_urls>"
],
"background": {
"service_worker": "dist/background.js",
"type": "module"
},
"icons": {
"16": "icons/icon-16.png",
"32": "icons/icon-32.png",
"48": "icons/icon-48.png",

Steps to Reproduce

1. Run opencli ...
2. ...
3. See error

Expected Behavior

please fix bug

OpenCLI Version

1.7.19

Node.js Version

22.x

Operating System

Linux

Logs / Screenshots

opencli doctor
opencli v1.7.19 doctor (node v24.14.1)

[OK] Daemon: running on port 19825 (v1.7.19)
[OK] Extension: connected (v1.0.12)

Profiles:
  • 4uqfv54e: connected v1.0.12
[OK] Connectivity: connected in 0.2s

Everything looks good!

  Update available: v1.7.19 → v1.7.21
  Run: npm install -g @jackwener/opencli
-------
opencli doctor
⏳ Waiting for Chrome/Chromium extension to connect...
   Make sure Chrome or Chromium is open and the OpenCLI extension is enabled.
opencli v1.7.21 doctor (node v22.22.2)

[OK] Daemon: running on port 19825 (v1.7.21)
[MISSING] Extension: not connected
[FAIL] Connectivity: failed (Browser Bridge extension not connected)

Issues:
  • Daemon is running but the Chrome/Chromium extension is not connected.
If the extension is already installed, try: opencli daemon restart
If the extension is not installed:
  1. Download from https://github.com/jackwener/opencli/releases
  2. Open chrome://extensions/ → Enable Developer Mode
  3. Click "Load unpacked" → select the extension folder
  • Browser connectivity test failed: Browser Bridge extension not connected

[zhudy]

here is some more details to update: the root-cause might be chromium: as I upgrade opencli and extension to latest v1.0.15 with v1.7.21, Chromium Version 146.0.7680.153 (Official Build) Alpine Linux (64-bit) work both, but Chrome Version 147.0.7727.101 (Official Build) built on Ubuntu Resolute Raccoon (development branch) (64-bit) do not work

[jackwener]

Thanks for the details. Initial triage: this does not look like a missing-file/package issue in the release zip. The v1.0.15 zip contains dist/background.js, the manifest still points to that file, and compared with the previous extension package the manifest change is only the extension version. The background script also parses locally.\n\nThe extra detail that v1.0.15 works in Chromium 146 on Alpine but fails in Chrome 147 on Ubuntu development branch points to either a Chrome 147 extension-service-worker regression or a runtime exception during service worker startup that only that Chrome build exposes.\n\nCould you open chrome://extensions, enable Developer mode, click the OpenCLI extension's service worker / errors link, and paste the first actual exception line/stack? The current "Service worker registration failed. Status code: 2" message is too generic; the service worker console error should identify whether this is a Chrome 147 bug or one of our startup paths.\n\nTemporary workaround: use Chromium/Chrome stable where v1.0.15 loads, or keep the older extension package if it still connects to your daemon. We will keep this issue open until we have the service worker startup error.