AI 产品解读Browser automation bridge between the OpenCLI CLI tool and Chrome, enabling remote browser control via a local daemon
Allows developers to programmatically control Chrome browser tabs (navigate, execute JS, take screenshots, manage cookies, capture network traffic, manipulate DOM, handle downloads) from the command line via the opencli CLI tool
User installs the OpenCLI CLI tool and this Chrome extension. The CLI spawns a local daemon process on localhost:19825. The extension connects to this daemon via WebSocket. When the user runs opencli commands in the terminal, the daemon relays browser automation commands (exec, navigate, screenshot, cookies, cdp, etc.) to the extension, which executes them using Chrome's debugger API on managed tab leases, and returns results back through the daemon to the CLI.
Executes JavaScript in browser tabs via Chrome Debugger Protocol (CDP)Page navigation and tab management with session-based leasesScreenshot capture with configurable viewportCookie read/write operationsNetwork request capture and inspectionDOM querying and file input automation
- 目标用户
- Developers using CLI-based browser automation / QA engineers running automated browser tests / DevOps engineers needing headless browser control
- The extension is bundled/minified (dist/background.js), so some implementation details may be obscured, though the code is readable enough for functional analysis
- Could not verify if the OpenCLI CLI tool itself requires login or has paid tiers — this analysis covers only the Chrome extension package
付费分析未识别到付费功能
No references to premium, payment, billing, subscription, license, stripe, checkout, purchase, or upgrade found anywhere in the codebase. All 'pro' keyword hits were false positives from JavaScript Promise code. The extension is a free open-source tool (GitHub: jackwener/opencli) with no feature gating or payment flows.
- 置信度
- 95
- 支付平台
- --
- 来源
- AI / 高
- 需要登录
- 否
- 登录理由
- No login, authentication, account creation, or credential flow exists in the extension. The extension connects to a local daemon via WebSocket on localhost:19825 with no auth handshake — just a 'hello' message with version info. All 'session' keyword hits refer to browser automation tab-lease sessions, not user login sessions. The popup only shows daemon connection status, not any login UI.