Overview
OpenCLI gives one surface to three kinds of automation. Built-in adapters expose sites such as Hacker News, Reddit, Twitter/X, Bilibili, Zhihu and Xiaohongshu as ordinary commands — `opencli hackernews top --limit 5` — so a scripted task gets a deterministic interface instead of a live browser session. Where no adapter exists, `opencli browser` primitives let an agent navigate, click, type, extract and inspect any page directly.
The key design choice is that it drives the Chrome you are already signed into. A lightweight Browser Bridge extension plus a small local daemon connect OpenCLI to your profile, so an agent works with your existing logins rather than re-authenticating or handling credentials. Multiple Chrome profiles are supported: you list the connected contexts, give them aliases, and select one per command — with several connected and no default set, OpenCLI asks rather than guessing.
It is also a hub for things that are not websites. Local binaries can be registered and exposed through the same discovery surface (`gh`, `docker`, Notion, Telegram and others), and desktop adapters cover Electron apps like Cursor, Codex, ChatGPT, Trae and Antigravity. For agents, the project ships installable skills — `opencli-browser` for ad-hoc page driving, `opencli-adapter-author` for writing a reusable adapter end to end, `opencli-autofix` for repairing a broken one, plus sitemap skills for navigating a site with recorded structure.
What it does
- Built-in adapters turning popular sites into deterministic CLI commands
- `opencli browser` primitives — navigate, click, type/fill, extract, inspect — over your logged-in Chrome
- Browser Bridge extension plus a local daemon that auto-starts when needed
- Named Chrome profiles with per-command selection, so multi-profile setups are explicit
- Agent skills: opencli-browser, opencli-adapter-author, opencli-autofix and the sitemap pair
- CLI hub for local binaries (`opencli external register`) and adapters for Electron desktop apps
- Plugin system for publishing or installing third-party commands from a Git repo
Getting started
Install the CLI, add the browser bridge extension, verify the setup with the built-in doctor, then run your first command. Node.js >= 20.18.1 is required for the npm install path.
Install OpenCLI
OpenCLIApp is recommended on macOS and Windows (it bundles the runtime and a tray UI); the npm global install is the CLI-only path for CI and servers.
node --version
npm install -g @jackwener/opencliAdd the Browser Bridge extension
Install OpenCLI from the Chrome Web Store, or load the unpacked extension from a GitHub release zip via chrome://extensions with Developer mode enabled.
https://chromewebstore.google.com/detail/opencli/ildkmabpimmkaediidaifkhjpohdnifkVerify the setup
The doctor diagnoses browser connectivity and the daemon.
opencli doctorName your Chrome profiles
Each Chrome profile runs its own extension instance. With one connected profile OpenCLI uses it automatically.
opencli profile list
opencli profile rename <contextId> work
opencli profile use work
opencli --profile work browser main stateRun your first commands
`opencli list` shows every registered command, built-in or generated.
opencli list
opencli hackernews top --limit 5
opencli bilibili hot --limit 5Install the agent skills
Installs into your AI agent (Claude Code, Cursor and others); re-running refreshes an existing install.
npx skills add jackwener/opencli
# or only what you need
npx skills add jackwener/opencli --skill opencli-browserCommands and code are distilled from the project's own documentation — always check the official repo for the latest.
When to use it
- Let an agent act on a site that has no API, using your existing session instead of credentials
- Replace brittle scraping with a deterministic command for a site you query repeatedly
- Write and verify a reusable adapter for a new site with the adapter-author skill
- Expose local binaries and Electron apps through one discovery surface an agent can enumerate
How OpenCLI compares
OpenCLI alongside other open-source computer & browser use tools AI/TLDR tracks, ranked by GitHub stars.
| Tool | Stars | What it does |
|---|---|---|
| Browser Use | ★ 115k | A Python library that lets agents control a real browser to read pages and complete tasks online from natural-language instructions. |
| Open Interpreter | ★ 68.4k | A lightweight coding agent that runs code on your own computer to carry out tasks from natural-language requests. |
| Chrome DevTools MCP | ★ 52.2k | The Chrome team's MCP server that lets a coding agent control and inspect a live Chrome browser — performance traces, network requests, console messages and Puppeteer-backed automation. |
| UI-TARS Desktop | ★ 39k | ByteDance's multimodal agent stack and desktop app that controls a computer's graphical interface using vision-language models. |
| AIHawk | ★ 31.6k | Browser agent on a stealth Firefox that takes plain-language tasks and clicks, types and reads real pages - usable as an MCP server from Claude Code, Codex or Gemini CLI, or via its own web UI. |
| CloakBrowser | ★ 31.5k | Stealth Chromium build with source-level fingerprint patches that drops into Playwright or Puppeteer code, so agents and scrapers browse without tripping bot detection. |
| OpenCLI | ★ 29.4k | Turns websites into CLI commands and lets agents drive your logged-in Chrome |
| Page Agent | ★ 29.1k | Alibaba's in-page GUI agent: a JavaScript library you drop into a web page so users can drive its interface in natural language, working through text-based DOM manipulation rather than screenshots. |