[Bug]: OPENCLI_DAEMON_PORT is no longer supported (received 19825)

[bitorangej]

Description

> opencli doctor

error: OPENCLI_DAEMON_PORT is no longer supported (received 19825). The OpenCLI Chrome extension can only connect to localhost:19825. Unset OPENCLI_DAEMON_PORT and rerun opencli.

I have installed the latest OpenCLI APP and Chrome Exetention.

Steps to Reproduce

1. Run opencli doctor
2. See error

Expected Behavior

connect successfully

OpenCLI Version

can't execute

Node.js Version

20.x

Operating System

macOS

Logs / Screenshots

[itsmekeyan]

hey opencli team, whats the fix for this?? pls do proper testing, so this is so much waste of time for us??

[tizerluo]

Some findings from debugging this on macOS (OpenCLIApp 0.1.35, pkg install) that may help people who are stuck, plus one thing the app team may want to pick up:

Root cause is already fixed on the CLI side in v1.8.6 (PR #2074, "tolerate OPENCLI_DAEMON_PORT at the default port"), but OpenCLIApp 0.1.35 still bundles CLI 1.8.5, so app-managed installs stay broken until an app release ships with a tolerant core. Two details we verified:

• The injection comes from the app server process: quitting/restarting the app doesn't help, and deleting browserBridge.daemonPort from ~/Library/Application Support/BrowserBridge/state.json doesn't either — the server regenerates it on startup and injects OPENCLI_DAEMON_PORT=19825 into every CLI child it spawns.
• The menu-bar panel's "extension not connected" / "daemon not running" warning is misleading: the panel health-checks through the same broken managed path, so it stays yellow even when the daemon and extension are actually fine. opencli doctor is the source of truth.

Interim workaround (no npm install needed) — call the app's bundled runtime directly, bypassing the injecting server. Drop this in a PATH location that precedes /usr/local/bin (e.g. ~/.local/bin/opencli) and chmod +x it:

#!/bin/sh
unset OPENCLI_DAEMON_PORT
exec "/Applications/OpenCLIApp.app/Contents/Resources/node_modules/node/bin/node" \
  "/Applications/OpenCLIApp.app/Contents/Resources/node_modules/@jackwener/opencli/dist/src/main.js" "$@"

After this, the daemon starts on 19825, the extension connects, adapters and logged-in sessions work normally (opencli doctor all green). The app panel will keep showing the yellow warning — ignore it until an app update lands, then delete the wrapper to return to the managed shim.

Would be great to get an OpenCLIApp release bundling CLI >= 1.8.6 (or with the injection removed). Thanks!