PageAgent, A GUI agent that lives inside your web app

Name: PageAgent, A GUI agent that lives inside your web app
Availability: InStock
Author: simon_luv_pho

by simon_luv_pho·Mar 5, 2026·147 points·76 comments

Visit Project View on HN

AI Analysis

●●SolidShip ItBig Brain

DOM-native agent avoids external selenium; inherits user session but unclear if handles complex SPAs reliably.

Strengths

•Zero-backend deployment (one script tag) lowers barrier vs building agentic backends from scratch.
•Human-in-the-loop by default—agent asks before acting prevents blind automation mistakes common in web scraping bots.
•Bring-your-own-LLM (OpenAI, Claude, Ollama) avoids vendor lock-in and works fully offline with local models.

Weaknesses

•Browser-use and Playwright already do headless automation; unclear how PageAgent's DOM approach beats them for complex workflows.
•No benchmarks on accuracy for form-filling or multi-step workflows; claims feel aspirational without validation.

Post Description

Title: Show HN: PageAgent, A GUI agent that lives inside your web app

Hi HN,

I'm building PageAgent, an open-source (MIT) library that embeds an AI agent directly into your frontend.

I built this because I believe there's a massive design space for deploying general agents natively inside the web apps we already use, rather than treating the web merely as a dumb target for isolated bots.

Currently, most AI agents operate from external clients or server-side programs, effectively leaving web development out of the AI ecosystem. I'm experimenting with an "inside-out" paradigm instead. By dropping the library into a page, you get a client-side agent that interacts natively with the live DOM tree and inherits the user's active session out of the box, which works perfectly for SPAs.

To handle cross-page tasks, I built an optional browser extension that acts as a "bridge". This allows the web-page agent to control the entire browser with explicit user authorization. Instead of a desktop app controlling your browser, your web app is empowered to act as a general agent that can navigate the broader web.

I'd love to start a conversation about the viability of this architecture, and what you all think about the future of in-app general agents. Happy to answer any questions!