OpenCLI：让智能体操作网站和登录浏览器

Make Any Website into CLI & Use your logged-in browser by AI agent.

OpenCLI Convert any website into a CLI & run Browser Use on your logged-in Chrome. Turn websites and browser sessions into deterministic interfaces for humans and AI agents. Or run Browser Use against any page — navigate, fill forms, click, extract, automate. OpenCLI is a general-purpose browser automation CLI for AI agents and an agent-browser alternative. Navigate, inspect, click, fill forms, extract, and screenshot websites without a site adapter. Built-in adapters add reusable, deterministic site commands. See OpenCLI vs agent-browser and migration. OpenCLI gives you one surface for three different kinds of automation: Use built-in adapters for sites like Bilibili, Zhihu, Xiaohongshu, Reddit, HackerNews, Twitter/X, and many more. Let AI Agents operate any website — install the opencli-browser skill in your AI agent (Claude Code, Cursor, etc.), and it can navigate, click, type/fill, extract, and inspect any page through your logged-in browser via opencli browser primitives. Write new adapters end-to-end with opencli browser + the opencli-adapter-author skill, which guides from first recon through field decoding, code, and opencli adapter test. Agent command contract Commands default to JSON: { "ok": true, "data": ... }; failures return { "ok": false, "error": { "code": "...", "message": "...", "hint": "..." } } on stdout with a nonzero exit code. Logs use stderr. Explicit human formats, help, version and completion retain their own formats; browser follow modes use JSON Lines. opencli list search --site github opencli browser open https://example.com --session research opencli browser network --static --session research opencli browser chrome describe opencli adapter check github/search list returns compact, paginated capabilities (commands, total, nextOffset); read arguments with <command> --help -f json. Page scope is --session, native Chrome calls need no session. Adapter authoring is grouped under adapter init|check|test. state --diagnostics and network --static replace analyze and discover. This changes CLI syntax and JSON output. JS adapters keep cli({...}), func(args) and func(page, args); adapter defaultFormat no longer changes the CLI default. Quick Start 1. Install OpenCLI For desktop use, start with OpenCLIApp. It bundles the OpenCLI runtime, keeps the managed opencli command installed, and gives you a system tray UI for setup, diagnostics, updates, browser-login keepalive, and Web → Markdown. Option A — OpenCLIApp (recommended for macOS / Windows): Download the latest app from https://opencli.info/download, install it, then open the app once and use the System page to install or repair the opencli command. Option B — npm global install (CLI-only / CI / servers): OpenCLI requires Node.js >= 20.18.1 when installed through npm. node --version npm install -g @jackwener/opencli 2. Install the Browser Bridge Extension OpenCLI connects to Chrome/Chromium through a lightweight Browser Bridge extension plus a small local daemon. The daemon auto-starts when needed. Option A — Chrome Web Store (recommended): Install OpenCLI from the Chrome Web Store. Option B — Manual install: Download the latest opencli-extension-v{version}.zip from the GitHub Releases page. Unzip it, open chrome://extensions, and enable Developer mode. Click Load unpacked and select the unzipped folder. 3. Verify the setup opencli doctor 4. Optional: name your Chrome profile Each Chrome profile runs its own OpenCLI extension instance. If you use multiple Chrome profiles, list the connected profiles and assign local aliases: opencli profile list opencli profile rename <contextId> work opencli profile use work opencli --profile work browser main state With only one connected profile, OpenCLI uses it automatically. With multiple connected profiles and no default, OpenCLI asks you to choose instead of guessing. 5. Run your first commands opencli list opencli hackernews top --limit 5 opencli bilibili hot --limit 5 For Humans Use OpenCLI directly when you want a reliable command instead of a live browser session: opencli list shows every registered command. opencli <site> <command> runs a built-in or generated adapter. opencli doctor helps diagnose browser connectivity. Extending OpenCLI If you want to add your own commands, start with the Extending OpenCLI guide. README keeps this short; the guide covers the directory layout, source-control model, and install commands. Need Recommended path Keep personal website commands in your own Git repo opencli plugin create + opencli plugin install file://... Quickly draft a private local adapter opencli adapter init <site>/<command> in ~/.opencli/clis/ Modify an official adapter locally opencli adapter eject <site> + opencli adapter reset <site> Publish or install third-party commands opencli plugin install github:user/repo Close temporary browser tabs after use To remove temporary owned tabs when a workflow finishes: export OPENCLI_CLOSE_OWNED_TAB=1 opencli web read --url https://example.com --stdout true # Multi-step browser sessions stay open between calls; close explicitly at the end: opencli browser close --session research This opts into closing only the current lease's owned tab. Chrome closes its window automatically if no tabs remain; existing user pages and other sessions are preserved. Bound tabs are detached and kept open. The default reusable container policy, idle expiry, --keep-tab true, and persistent site sessions remain unchanged. Use --site-session ephemeral for one-shot reads of adapters that otherwise keep a persistent site session. Cleanup uses a dedicated action, so older extensions reject it without releasing the lease, and requires an extension acknowledgement. If cleanup fails or the extension is too old, a warning reports it separately from the site action. Retry explicit browser cleanup, or close a remaining one-shot adapter tab manually; do not repeat a completed site write. Explicit browser close also exits with an error; a one-shot adapter can still