OpenCLI vs page-agent
The two are close in size: 29.0k stars for OpenCLI, 29.0k for page-agent. Over the days we have tracked them OpenCLI moved +21.6% and page-agent +18.2%, so OpenCLI is growing faster right now.
They split the axes: OpenCLI leads on context depth and customization, page-agent on model freedom and setup ease.
Stars and commit dates come from our own daily tracking. The six axes are read off each project's documentation by our review pipeline, so they describe what a project says about itself, not what we measured in its code.
Where they stand today
Converts any website into a deterministic CLI and lets AI agents drive your logged-in Chrome via a local Browser Bridge and reusable adapter skills.
- Stars
- 29.0k
- Tracked growth
- +21.6%
- Maturity
- ●●●●●
- Last commit
- 5d ago
- Language
- JavaScript
- License
- Apache-2.0
- Cost to run
- Free, local runtime
An in-page GUI agent that runs entirely inside any web page with a single script, no extension or headless browser required.
- Stars
- 29.0k
- Tracked growth
- +18.2%
- Maturity
- ●●●●●
- Last commit
- 1d ago
- Language
- TypeScript
- License
- MIT
- Cost to run
- Demo testing LLM available; otherwise use your API key
Six axes, head to head
Each axis runs 0 to 5. The label under a score is what that project's own docs claim, not a category average.
| Axis | OpenCLI | page-agent |
|---|---|---|
Context depth How much of your codebase it sees before it answers: the open diff, the diff plus related files, or the whole repository. | ●●●●● Site & related files | ●●●●● Single-page only |
Noise control How it keeps output volume down — severity thresholds, deduplication, incremental runs over new commits only. | ●●●●● Basic diagnostics | ●●●●● No noise controls |
Customization How far it bends to your team: custom rules, prompts, style guides, per-path config. | ●●●●● Plugins & adapters | ●●●●● Config options |
Privacy Whether your code stays on your own infrastructure: fully local, self-hostable, or cloud API only. | ●●●●● Runs locally | ●●●●● Self-hostable |
Model freedom Whether you can point it at any provider, or it is wired to one. | ●●●●● Multiple providers | ●●●●● Bring-your-own-key |
Setup ease What it takes to get a first useful run out of it. | ●●●●● Install + extension | ●●●●● One-line integration |
Which one to pick
Pick OpenCLI if…
Local browser control — use your logged-in Chrome and a lightweight local daemon/extension so agents operate real pages and you can author reusable adapters and plugins.
- Context depth: Site & related files (3/5 against 1/5)
- Customization: Plugins & adapters (5/5 against 3/5)
Pick page-agent if…
Easy integration — one-line in-page script to add an AI copilot to any web app, with support for your own and locally deployed models.
- Model freedom: Bring-your-own-key (5/5 against 3/5)
- Setup ease: One-line integration (5/5 against 3/5)
What people want from each one
jackwener/OpenCLI
Hacker News: OpenCLI – Turn any website into a CLI, reusing your Chrome login drew 6 points and 3 comments.
alibaba/page-agent
Hacker News: Page-Agent.js: The GUI Agent Living in Your Webpage drew 3 points and 0 comments.
Questions people ask
Is OpenCLI better than page-agent?
They split the axes: OpenCLI leads on context depth and customization, page-agent on model freedom and setup ease. OpenCLI is worth picking when local browser control — use your logged-in Chrome and a lightweight local daemon/extension so agents operate real pages and you can author reusable adapters and plugins.
Which of OpenCLI and page-agent keeps my code private?
OpenCLI: Runs locally (5/5). page-agent: Self-hostable (4/5).
What does each one cost to run?
OpenCLI: Free, local runtime. page-agent: Demo testing LLM available; otherwise use your API key.
Full profiles: jackwener/OpenCLI and alibaba/page-agent. Everything else in Browser agents.