nanobrowser vs Page Agent
Side-by-side comparison of two AI agent tools
Short answer
- Page Agent is growing faster: +405 GitHub stars in the last 30 days vs +75 for nanobrowser.
- Pick nanobrowser for: open-Source Chrome extension for AI-powered web automation. Pick Page Agent for: javaScript in-page GUI agent.
From GitHub data refreshed daily.
n
nanobrowseropen-source
Open-Source Chrome extension for AI-powered web automation. Run multi-agent workflows using your own LLM API key. Alternative to OpenAI Operator.
P
Page Agentopen-source
JavaScript in-page GUI agent. Control web interfaces with natural language.
Metrics
| nanobrowser | Page Agent | |
|---|---|---|
| Stars | 13.9k | 29.3k |
| Star velocity /mo | 75 | 405 |
| Commits (90d) | 1 | 52 |
| Releases (6m) | 0 | 10 |
| Overall score | 0.3747190404133606 | 0.6656732657345861 |
FAQ
- Which is more popular, nanobrowser or Page Agent?
- Page Agent has more GitHub stars (29,315 vs 13,855).
- Which is more actively developed, nanobrowser or Page Agent?
- Page Agent had more commits in the last 90 days (52 vs 1).
- Should I use nanobrowser or Page Agent?
- Compare their capabilities, limitations and "best for" notes above. Both are open source, so trying each on a small task is the fastest way to decide.