Page Agent

What does this agent do, and when should you use it?

Page Agent is a JavaScript GUI-agent library that can be embedded in a web page. Developers can add PageAgent through a script or npm package and drive page interactions with natural-language instructions. It processes the DOM as text and does not require screenshots, multimodal models, or special permissions. Its stated boundary is client-side web enhancement rather than server-side automation; an optional Chrome extension supports cross-tab work, and a beta MCP Server enables external MCP clients to control the browser. The project supports bring-your-own models, including mainstream and locally deployed models according to the README.

After Page Agent is loaded, an application can create new PageAgent(...) with model, baseURL, apiKey, and an optional language. It then calls await agent.execute('Click the login button'), allowing the agent to carry out the requested interface action through a text representation of the page DOM. The quickest trial path loads page-agent.demo.js, which automatically creates a demo agent; adding ?autoInit=false disables that behavior so you can instantiate window.PageAgent yourself. The optional Chrome extension handles multi-tab browser tasks, while the beta MCP Server allows external MCP clients to control the browser.

1. A SaaS product team embedding a natural-language copilot in an existing web application without rewriting its backend.
2. An ERP, CRM, or admin-system user completing a form workflow that would otherwise take many clicks.
3. A user relying on voice commands or screen-reader-oriented access to operate a web application through natural language.
4. A browser user who needs a task to span multiple tabs and can use the optional Chrome extension.
5. A team using an MCP client to control a browser through the beta MCP Server.

What are this agent's strengths and limitations?

How do you install or deploy this agent?

Install the package with npm install page-agent. In browser-side code, import PageAgent and provide access to a model service, including its model name, baseURL, and apiKey. Alternatively, load the demo script directly: <script src="https://cdn.jsdelivr.net/npm/[email protected]/dist/iife/page-agent.demo.js" crossorigin="anonymous"></script>; its free testing LLM API is for technical evaluation only and is subject to its terms.

How do you use this agent?

Import PageAgent from the package, then create an agent with the model name, compatible model-service baseURL, API key, and optional language used by your page. The example below uses qwen3.5-plus, an en-US language value, and a compatible-mode API endpoint. After initialization, pass the natural-language instruction Click the login button to agent.execute(...); the agent performs the requested interface action through its text representation of the page DOM.

import { PageAgent } from 'page-agent'

const agent = new PageAgent({
  model: 'qwen3.5-plus',
  baseURL: 'https://dashscope.aliyuncs.com/compatible-mode/v1',
  apiKey: 'YOUR_API_KEY',
  language: 'en-US',
})

await agent.execute('Click the login button')

How does this agent compare with similar options?

FAQ