Troubleshooting

Common Issues

Ensure the opencli Browser Bridge extension is installed and enabled in chrome://extensions.
Run opencli doctor to diagnose connectivity.

Your login session in Chrome might have expired. Open a normal Chrome tab, navigate to the target site, and log in or refresh the page.
Some sites have geographic restrictions (e.g., Bilibili, Zhihu from outside China).

A healthy Browser Bridge connection does not guarantee that the current page target exposes the data your adapter expects.
Some browser adapters are sensitive to the active host or page context.
Example: opencli 1688 item may fail with did not expose product context if the target is too broad.
Retry on a real item page, refresh the page in Chrome, and if needed narrow the target, for example:

OPENCLI_CDP_TARGET=detail.1688.com opencli 1688 item 841141931191 -f json

Make sure you are using Node.js >= 20. Some dependencies require modern Node APIs.
Run node --version to verify.

# View extension logs
curl localhost:19825/logs

# Stop the daemon
opencli daemon stop

# Full diagnostics
opencli doctor

The daemon is persistent and stays alive until explicitly stopped (opencli daemon stop) or the package is uninstalled.

For Electron/CDP-based adapters (Cursor, Codex, etc.):

# Clean rebuild
rm -rf dist/
npm run build

# Type check
npx tsc --noEmit