StackMap
Subscribe

browser-use vs page-agent

The standard library for letting AI agents drive a real browser — click, type, fill forms and complete tasks from a natural-language goal. 100k+ stars, Python. — versus — Alibaba's in-page GUI agent: one script tag gives any webpage its own AI agent — users drive the interface in natural language. TypeScript, tiny bundle, Chrome extension available.

The curated verdict

Same end state — AI operating a web interface — from opposite sides of the fence: browser-use is the agent's browser for any site; page-agent is embedded by the site itself, giving its own users an agent.

browser-usepage-agent
Stars105k27k
Forks12k2.5k
LanguagePythonTypeScript
LicenseMITMIT
Last activityyesterdaytoday
Topicsagents, webagents, web
Curated connections71

browser-use — the curator's take

When the task lives behind login walls, forms and JavaScript — 'book this', 'apply to that', 'put these in my cart' — this is the default tool: it feeds the agent a cleaned DOM, executes its clicks/typing, and recovers from the endless weirdness of real websites. Install-as-skill support means Claude Code/Cursor agents pick it up in one prompt. NOT for bulk data extraction — an LLM driving a browser is the slowest, most expensive way to scrape a thousand pages (use a crawler); and treat any agent-with-a-browser as having the keys to whatever it's logged into — sandbox accordingly.

page-agent — the curator's take

The inverted take on browser agents: instead of YOUR agent driving SOMEONE's site, the site ships its own — one script tag and visitors can say 'file an expense report for Tuesday's taxi' at your UI. For products with deep, form-heavy interfaces this is the cheapest 'AI feature' with real utility, and 26k stars say the demand is real. NOT for automating third-party sites (that's browser-use's job — this requires the site owner to opt in), and handing an LLM the ability to click your own UI means auditing what it can reach: same-origin power cuts both ways.