mirror of https://github.com/jackwener/OpenCLI.git synced 2026-09-14 18:25:42 +08:00

Files

T

zhengyu fbdb1b24dc fix(browser): harden multi-tab routing and target isolation (#1072 )

* fix(browser): harden multi-tab routing and target isolation

- make daemon command ids collision-resistant and retry duplicate pending ids\n- add validated tab list/new/select/close flows with persisted default targets\n- keep untargeted browser commands on the default tab unless tab select changes it\n- document tab targeting and add unit, extension, and e2e coverage for concurrent multi-tab execution

* fix(browser): keep default tab stable after tab new

* fix(browser): close remaining tab routing gates

* docs(browser): align target id wording

* docs(browser): refine target id examples

---------

Co-authored-by: jackwener <jakevingoo@gmail.com>

2026-04-19 18:48:45 +08:00

3.1 KiB

Raw Permalink Blame History

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://extensions and 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

Tab Targeting

Browser commands run inside the shared browser:default workspace unless you explicitly choose another tab target.

opencli browser open https://www.baidu.com/
opencli browser tab list
opencli browser tab new https://www.baidu.com/
opencli browser eval --tab <targetId> 'document.title'
opencli browser tab select <targetId>
opencli browser get title
opencli browser tab close <targetId>

Key rules:

opencli browser open <url> and opencli browser tab new [url] return a targetId.
opencli browser tab list prints the targetId values of tabs that already exist.
--tab <targetId> routes a single browser command to that specific tab.
tab new creates a new tab but does not change the default browser target.
tab select <targetId> makes that tab the default target for later untargeted opencli browser ... commands.
tab close <targetId> removes the tab; if it was the current default target, the stored default is cleared.

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.

3.1 KiB Raw Permalink Blame History