jakevin
feedaf93b4
* fix: remove duplicate extension zip from releases
The release and build-extension workflows were creating both
opencli-extension.zip and opencli-extension-v{version}.zip (identical
content), causing both to be uploaded. Keep only the versioned filename.
* docs: update extension zip filename to versioned format
Update all references from opencli-extension.zip to
opencli-extension-v{version}.zip to match the workflow change.
2.1 KiB
Browser Bridge Setup
⚠️ Important: Browser commands reuse your Chrome login session. You must be logged into the target website in Chrome before running commands.
OpenCLI connects to your browser through a lightweight Browser Bridge Chrome Extension + micro-daemon (zero config, auto-start).
Extension Installation
Method 1: Download Pre-built Release (Recommended)
- Go to the GitHub Releases page and download the latest
opencli-extension-v{version}.zip. - Unzip the file and open
chrome://extensions, enable Developer mode (top-right toggle). - Click Load unpacked and select the unzipped folder.
Method 2: Load Unpacked Source (For Developers)
- Open
chrome://extensionsand enable Developer mode. - Click Load unpacked and select the
extension/directory from the repository.
Verification
That's it! The daemon auto-starts when you run any browser command. No tokens, no manual configuration.
opencli doctor # Check extension + daemon connectivity
How It Works
┌─────────────┐ WebSocket ┌──────────────┐ Chrome API ┌─────────┐
│ opencli │ ◄──────────────► │ micro-daemon │ ◄──────────────► │ Chrome │
│ (Node.js) │ localhost:19825 │ (auto-start) │ Extension │ Browser │
└─────────────┘ └──────────────┘ └─────────┘
The daemon manages the WebSocket connection between your CLI commands and the Chrome extension. The extension executes JavaScript in the context of web pages, with access to the logged-in session.
Daemon Lifecycle
The daemon auto-starts on first browser command and stays alive persistently.
opencli daemon stop # Graceful shutdown
The daemon is persistent — it stays alive until you explicitly stop it (opencli daemon stop) or uninstall the package.