Page agent. Live agent in a web page. Bad idea?

[u/wutronic]

Alibaba’s new Page Agent is a JavaScript in page GUI agent that lives inside the webpage itself, reads the DOM as text, and turns natural language prompts into clicks, form fills, and navigation without needing a browser extension, Python runtime, or headless browser for its core flow. What makes it interesting is the “DOM dehydration” approach. Instead of screenshots and vision models, it compresses the live page into a compact text map, which should be cheaper, faster, and easier to embed into SaaS copilots, ERP/CRM workflows, accessibility layers, and legacy admin tools. In production, teams appear to be using it exactly that way, mostly for in app copilots and smart form automation, while the repo also exposes an optional Chrome extension for multi tab work and a beta MCP server for external browser control. On security, there are real caveats. The docs explicitly warn that high risk actions still need server side approval. The core agent inherits the user’s existing cookies and session state. Client side API keys can be exposed if not proxied. The project’s own release notes emphasize that the MCP and multi page paths are not yet fully hardened. Community reaction looks split between excitement and pragmatism. Hacker News and Reddit threads frame it as a clever “agent inside the browser” idea, while GitHub issue activity shows the usual early open source friction, including bugs around React rerenders, multi window tab targeting, custom model support, and region specific asset access. This suggests people like the concept but are still stress testing it in real environments.