page-agent vs webcmd
page-agent is much bigger: 29.2k stars against 2.5k. Over the days we have tracked them page-agent moved +19% and webcmd +114.7%, so webcmd is growing faster right now.
page-agent leads on model freedom and setup ease. webcmd does not take any axis by a clear margin.
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
An in-page GUI agent that runs entirely inside any web page with a single script, no extension or headless browser required.
- Stars
- 29.2k
- Tracked growth
- +19%
- Maturity
- ●●●●●
- Last commit
- 3d ago
- Language
- TypeScript
- License
- MIT
- Cost to run
- Demo testing LLM available; otherwise use your API key
Learns site navigation and compiles it into reusable deterministic commands so agents stop rediscovering the web and greatly reduce token spend.
- Stars
- 2.5k
- Tracked growth
- +114.7%
- Maturity
- ●●●●●
- Last commit
- 20m ago
- Language
- TypeScript
- License
- Apache-2.0
- Cost to run
- Free to run locally; optional hosted cloud
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 | page-agent | webcmd |
|---|---|---|
Context depth How much of your codebase it sees before it answers: the open diff, the diff plus related files, or the whole repository. | ●●●●● Single-page only | ●●●●● Diff only |
Noise control How it keeps output volume down — severity thresholds, deduplication, incremental runs over new commits only. | ●●●●● No noise controls | ●●●●● Minimal controls |
Customization How far it bends to your team: custom rules, prompts, style guides, per-path config. | ●●●●● Config options | ●●●●● Plugin & config |
Privacy Whether your code stays on your own infrastructure: fully local, self-hostable, or cloud API only. | ●●●●● Self-hostable | ●●●●● Self-hostable |
Model freedom Whether you can point it at any provider, or it is wired to one. | ●●●●● Bring-your-own-key | ●●●●● Several providers |
Setup ease What it takes to get a first useful run out of it. | ●●●●● One-line integration | ●●●●● CLI install |
Which one to pick
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)
Pick webcmd if…
Cost-saving — use learned, deterministic browser adapters to cut agent token and browsing variance while running locally or via optional cloud.
What people want from each one
alibaba/page-agent
Hacker News: Page-Agent.js: The GUI Agent Living in Your Webpage drew 3 points and 0 comments.
agentrhq/webcmd
Questions people ask
Is page-agent better than webcmd?
page-agent leads on model freedom and setup ease. webcmd does not take any axis by a clear margin. page-agent is worth picking when 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.
Which of page-agent and webcmd keeps my code private?
page-agent: Self-hostable (4/5). webcmd: Self-hostable (4/5).
What does each one cost to run?
page-agent: Demo testing LLM available; otherwise use your API key. webcmd: Free to run locally; optional hosted cloud.
Full profiles: alibaba/page-agent and agentrhq/webcmd. Everything else in Browser agents.