AIHawk vs page-agent
The two are close in size: 30.3k stars for AIHawk, 29.0k for page-agent.
page-agent leads on model freedom and setup ease. AIHawk 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
Drives a real, patched Firefox browser over MCP or OpenRouter so the agent can click, type and read actual web pages for automation rather than relying on APIs or scraped data.
- Stars
- 30.3k
- Tracked growth
- not tracked long enough
- Maturity
- ●●●●●
- Last commit
- 9h ago
- Language
- Python
- License
- MIT
- Cost to run
- Your OpenRouter API key or assistant-provided model
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 | AIHawk | 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. | ●●●●● No repo access | ●●●●● Single-page only |
Noise control How it keeps output volume down — severity thresholds, deduplication, incremental runs over new commits only. | ●●●●● None mentioned | ●●●●● No noise controls |
Customization How far it bends to your team: custom rules, prompts, style guides, per-path config. | ●●●●● Config & flags | ●●●●● Config options |
Privacy Whether your code stays on your own infrastructure: fully local, self-hostable, or cloud API only. | ●●●●● Cloud API key | ●●●●● Self-hostable |
Model freedom Whether you can point it at any provider, or it is wired to one. | ●●●●● OpenRouter / MCP | ●●●●● Bring-your-own-key |
Setup ease What it takes to get a first useful run out of it. | ●●●●● Config + API key | ●●●●● One-line integration |
Which one to pick
Pick AIHawk if…
Real browser automation — pick AIHawk when you need an agent that interacts with complex web pages (mouse, keyboard, real page rendering) and can integrate with your assistant or OpenRouter.
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
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 AIHawk better than page-agent?
page-agent leads on model freedom and setup ease. AIHawk does not take any axis by a clear margin. AIHawk is worth picking when real browser automation — pick AIHawk when you need an agent that interacts with complex web pages (mouse, keyboard, real page rendering) and can integrate with your assistant or OpenRouter.
Which of AIHawk and page-agent keeps my code private?
AIHawk: Cloud API key (3/5). page-agent: Self-hostable (4/5).
What does each one cost to run?
AIHawk: Your OpenRouter API key or assistant-provided model. page-agent: Demo testing LLM available; otherwise use your API key.
Full profiles: feder-cr/AIHawk and alibaba/page-agent. Everything else in Browser agents.