Description
我在 VPS 上部署了 opencli，升级到 1.8 之前还能稳定保持和 chrome extension 的连接，现在已经一直无法连接了。但是我VNC 到服务器手动打开 Chrome，可以连上，一切正常。
Steps to Reproduce
- deploy opencli on a remote vps, install both chrome and extension
- ssh to server, exec "opencli doctor"
- See error
Expected Behavior
expect opencli extension behave the same way both local and remote
OpenCLI Version
1.8.0
Node.js Version
22.x
Operating System
Linux
Logs / Screenshots
ubuntu@VM-0-7-ubuntu:~/Desktop$ opencli doctor -v
⏳ Waiting for Chrome/Chromium extension to connect...
Make sure Chrome or Chromium is open and the OpenCLI extension is enabled.
opencli v1.8.0 doctor (node v22.22.2)
[OK] Daemon: running on port 19825 (v1.8.0)
[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
Description
我在 VPS 上部署了 opencli，升级到 1.8 之前还能稳定保持和 chrome extension 的连接，现在已经一直无法连接了。但是我VNC 到服务器手动打开 Chrome，可以连上，一切正常。
Steps to Reproduce
Expected Behavior
expect opencli extension behave the same way both local and remote
OpenCLI Version
1.8.0
Node.js Version
22.x
Operating System
Linux
Logs / Screenshots