Windows install: Chrome extension enabled but no daemon starts on localhost:19825, so browser mode never connects

[pumpfake201-hub]

Summary

On Windows, I installed opencli-rs from the latest GitHub release and loaded the Chrome extension from the release zip. Chrome is detected and auth token is saved successfully, but browser mode still fails because nothing is listening on localhost:19825.

The extension tries to connect to:

ws://localhost:19825/ext

and gets:

ERR_CONNECTION_REFUSED

Environment

• OS: Windows
• Browser: Chrome
• opencli-rs installed from latest Windows release zip
• Chrome extension loaded unpacked from opencli-rs-chrome-extension.zip

What I did

1. Installed Windows binary:

   Invoke-WebRequest -Uri "https://github.com/nashsu/opencli-rs/releases/latest/download/opencli-rs-x86_64-pc-windows-msvc.zip" -OutFile opencli-rs.zip
   Expand-Archive opencli-rs.zip -DestinationPath .
   Move-Item .\opencli-rs.exe "$env:LOCALAPPDATA\Microsoft\WindowsApps\"
   

Verified binary:

Copy
where.exe opencli-rs
opencli-rs --help
Loaded Chrome extension from the release package and enabled it.

Ran auth:

Copy
opencli-rs auth
Token was saved successfully to:
C:\Users\gorko.opencli-rs\config.json

Ran diagnostics:

Copy
opencli-rs doctor
Actual result
opencli-rs doctor shows:

✓ Chrome/Chromium
✗ Daemon running
✗ Chrome extension connected
netstat -ano | findstr 19825 shows nothing listening on port 19825.

The Chrome extension service worker shows connection attempts to:
ws://localhost:19825/ext
failing with:
ERR_CONNECTION_REFUSED

Expected result
After installing the Windows binary + extension, either:

the daemon should auto-start and listen on localhost:19825, or
the docs/CLI should clearly expose the required step to start/register the daemon.
Additional observations
The Windows release zip appears to contain only:
opencli-rs.exe
No extra helper/native-host/daemon binary was included.
The extension package appears to contain only:
manifest.json
dist/background.js
icons
So I may be missing an undocumented Windows-specific daemon/bootstrap step, or this may be a packaging/docs issue.

Question
What is the correct Windows-side step to start/register the browser daemon that the extension expects on localhost:19825?