Make Any Website into CLI & Use your logged-in browser by AI agent.
26.4k
Stars
2.6k
Forks
215
Open issues
30
Contributors
AI Analysis
OpenCLI converts websites into CLI interfaces and enables AI agents to automate browser interactions through a logged-in Chrome session via Playwright-based browser automation. It serves developers and AI agent builders who need deterministic programmatic access to websites, built-in adapters for popular platforms (Reddit, Twitter, HackerNews, etc.), and extensibility for custom integrations.
Inferred from signals mentioned in the README (tests, CI, type safety) — not a review of the actual code.
AI's overall editorial judgment — not an average of the bars above, can weigh other factors too.
OpenCLI turns any website into a terminal command by bridging your logged-in Chrome to AI agents and human scripts
OpenCLI solves the friction of automating authenticated web sessions without writing full browser automation scripts. It targets developers, power users, and AI agent workflows (Claude Code, Cursor) who want to interact with websites — Bilibili, Reddit, Zhihu, HackerNews, Twitter/X — through deterministic CLI commands while reusing an existing logged-in Chrome profile. The tool covers three use cases: built-in site adapters, AI agent browser primitives, and a plugin system for custom adapters. It appears oriented toward East Asian developer communities given its Chinese-language docs and included adapters, but also targets Western tools.
Created in March 2026, this is a young project — roughly 3 months old at evaluation date. It emerged amid a broader wave of AI-agent browser automation tools, positioning itself at the intersection of CLI usability and LLM agent tooling rather than as a pure browser automation framework.
25,097 stars in ~3 months is rapid growth. 521 stars in the last 7 days indicates sustained, ongoing interest rather than a single viral spike. Growth likely driven by the AI agent tooling trend, the appeal of reusing authenticated browser sessions without re-login flows, and active promotion in developer communities. Chinese documentation and China-specific site adapters suggest strong traction in East Asian developer circles.
Chrome Web Store listing (opencli extension ID documented), published npm package (@jackwener/opencli), and a dedicated website (opencli.info) with a downloadable desktop app for macOS/Windows all suggest real deployment infrastructure. However, independent production usage reports, download counts, or case studies are not available in the provided metadata. Adoption plausible but not independently verified at scale.
Appears to follow a layered architecture: a Node.js CLI runtime, a Chrome extension acting as a browser bridge, a local daemon for extension communication, and a plugin/adapter registry. Skills are installable modules for AI agents. Likely uses CDP (Chrome DevTools Protocol) or a similar mechanism under the hood for browser control, but this is not confirmed in the README. The adapter model appears declarative with an eject/reset lifecycle.
not documented in README
Last push was 2026-06-24, the same day as evaluation — indicating very active, current maintenance. A 3-month-old project with daily pushes and 521 stars/week suggests a developer actively iterating. README is detailed, versioned npm package exists, Chrome Web Store listing exists, and a dedicated download site (opencli.info) is referenced — all signs of sustained investment.
ADOPT IF: you want to automate authenticated websites from a terminal or AI agent (Claude Code, Cursor) without managing separate browser login flows, and you are comfortable with a young, JavaScript/Node.js-based tool still maturing. AVOID IF: you need a battle-tested, production-hardened browser automation layer for enterprise workflows, or if Python/Rust-based ecosystems are mandatory in your stack. MONITOR IF: you are evaluating browser-automation tooling for AI agent pipelines but want to wait for the project to accumulate more real-world production case studies and a more established plugin ecosystem.
Independent dimensions
Mainstream potential
6/10
Technical importance
7/10
Adoption evidence
3/10
- Project is only ~3 months old; API surface, plugin contracts, and skill formats may change significantly before stabilizing.
- Dependency on a Chrome extension and local daemon introduces a fragile setup path — Chrome extension updates or browser policy changes could break the bridge without notice.
- Heavy reliance on logged-in Chrome profiles creates a security concern: a compromised agent skill or malicious plugin could exfiltrate authenticated sessions.
- Built-in adapters targeting specific sites (Bilibili, Xiaohongshu, Zhihu) may break silently when those sites update their front-end structure, creating ongoing maintenance burden.
- Ecosystem fragmentation risk: the similar-repo landscape (5 close competitors with large star counts) suggests the space is crowded and a consolidation around one or two tools is plausible, potentially stranding OpenCLI's adapter ecosystem.
Likely to grow into a meaningful tool for AI-agent-driven web automation within developer communities, especially in East Asia. Mainstream potential depends on whether the plugin ecosystem gains enough third-party contributors to reduce maintenance burden on the core author.
Newsletter
Get analyses like this every Monday
Free weekly digest of the most interesting open-source discoveries.
Languages
Information
- Website
- https://opencli.info/
- Language
- JavaScript
- License
- Apache-2.0
- Last updated
- 6d ago
- Created
- 4mo ago
- Analyzed with
- anthropic/claude-haiku-4-5
Stars over time
Contributors over time
Top 100 contributors only — repos with more will plateau at 100.
Open issues
Top contributors
Similar repos
microsoft/playwright-cli
Playwright CLI is a command-line interface for Playwright browser automation,...
ntegrals/openbrowser
Open Browser is a TypeScript framework that enables AI agents to autonomously...
JCodesMore/ai-website-cloner-template
A TypeScript-based template that automates website cloning by using AI coding...
| Repository | Stars | Week Δ | Language | Score | Updated |
|---|---|---|---|---|---|
|
jackwener/OpenCLI
this
|
26.4k | +516 | JavaScript | 8/10 | 6d ago |
|
microsoft/playwright-cli
|
11.9k | — | JavaScript | 8/10 | 19h ago |
|
ntegrals/openbrowser
|
9.5k | — | TypeScript | 8/10 | 3mo ago |
 hyperbrowserai/HyperAgent
|
1.5k | — | TypeScript | 7/10 | 2mo ago |
|
JCodesMore/ai-website-cloner-template
|
27.3k | — | TypeScript | 8/10 | 6d ago |
 nashsu/AutoCLI
|
2.9k | — | Rust | 7/10 | 3mo ago |
CLI-Anything has more stars and a larger community but appears Python-first. OpenCLI differentiates by focusing on reusing existing authenticated Chrome sessions and providing an AI agent skill system, rather than requiring a separate browser instance.
agent-browser is Rust-based, suggesting a performance focus and likely a lower-level API. OpenCLI's Node.js stack and high-level adapter model lower the bar for JavaScript developers and AI agent integration, at the cost of raw performance.
Closer in spirit and language stack. OpenCLI adds the CLI adapter registry, plugin ecosystem, and explicit AI-agent skills layer on top of browser automation, which openbrowser does not appear to offer based on available metadata.
Focused on cloning/templating websites rather than live session automation. OpenCLI's authenticated-session reuse is a distinct capability that ai-website-cloner-template does not address.
Significantly fewer stars and appears narrower in scope. OpenCLI's multi-site adapter registry and AI agent skill system give it broader coverage, though bb-browser may offer simpler setup for single-site use cases.
