Skip to main content
Browser Operator is Zeus’s browser automation extension, enabling AI Agents to control the user’s browser to perform automated tasks.

​
Overview

Browser Operator is implemented as a Chrome extension, allowing AI to:
  • Navigate to web pages
  • Click elements
  • Fill out forms
  • Extract content
  • Take screenshots
  • Execute JavaScript

​
Installation

​
From Chrome Web Store

  1. Visit the Chrome Web Store
  2. Search for “Zeus Browser Operator”
  3. Click “Add to Chrome”
  4. Confirm installation

​
Developer Mode Installation

  1. Download the extension source code
  2. Open chrome://extensions
  3. Enable “Developer mode”
  4. Click “Load unpacked”
  5. Select the extension directory

​
Architecture

​
Connection Flow

​
1. Install Extension

After installation, the extension displays a Zeus icon in the toolbar.

​
2. Login and Authorization

  1. Click the extension icon
  2. Log in to your Zeus account (or scan QR code to log in)
  3. Authorize extension access

​
3. Establish Connection

​
Supported Actions

ActionDescriptionParameters
browser_navigateNavigate to URLurl
browser_backGo back-
browser_forwardGo forward-
browser_refreshRefresh page-

​
Element Interaction

ActionDescriptionParameters
browser_clickClick elementref
browser_typeAppend text inputref, text
browser_fillClear and input textref, text
browser_selectSelect dropdown optionref, value
browser_hoverHover mouseref

​
Page Actions

ActionDescriptionParameters
browser_scrollScroll pagedirection, amount
browser_screenshotTake screenshotfullPage
browser_get_textGet element textref
browser_snapshotGet page structure-

​
Advanced Actions

ActionDescriptionParameters
browser_waitWait for specified timeseconds
browser_execute_jsExecute JavaScriptscript
browser_handle_dialogHandle dialogaccept, promptText

​
Element References (ref)

Browser Operator uses element references (refs) to identify page elements.

​
Getting a ref

Use browser_snapshot to get the page structure, which returns an element list with refs. Each element includes a ref (unique identifier), tag (HTML tag), text (element text), and more.

​
Using a ref

After obtaining a ref, you can use it in subsequent actions (such as browser_click, browser_fill) to precisely locate the target element.

​
Security Mechanisms

​
Permission Control

  • Per-action approval - Each action can be configured to require user confirmation
  • Domain restrictions - Restrict actions to specific domains only
  • Action logging - All actions are logged

​
Sandbox Environment

  • The extension runs in a sandbox environment
  • Cannot access sensitive browser data (such as passwords or cookies)
  • Cannot access data from other extensions

​
Authentication Security

  • Uses JWT Token authentication
  • Tokens are refreshed periodically
  • Supports device revocation

​
Use Cases

​
Automated Form Filling

User: Help me fill out this registration form

Zeus: I'll use Browser Operator to fill out the form automatically.
1. First, get the page structure...
2. Locate input fields and fill in the information...
3. Click the submit button...

​
Web Data Extraction

User: Extract all product information from this page

Zeus: I'll extract the page data.
1. Analyze the page structure...
2. Locate product elements...
3. Extract names, prices, descriptions...

​
Automated Testing

User: Test this login flow

Zeus: I'll execute a login test.
1. Navigate to the login page...
2. Enter test credentials...
3. Click login...
4. Verify login success...

​
Troubleshooting

​
Extension Shows “Not Connected”

  1. Check if you’re logged in
  2. Refresh the extension (click refresh on chrome://extensions)
  3. Check if the WebSocket server is running
  4. Check browser console for errors

​
Action Execution Failed

  1. Ensure the page has fully loaded
  2. Check if the element ref is valid
  3. Try using browser_snapshot to refresh the element list
  4. Check if a popup is blocking the action

​
Blank Screenshot

  1. Wait for page rendering to complete
  2. Check for iframe content
  3. Try using fullPage: false parameter

​
MCP Server

Browser Operator also runs as an MCP server and can be invoked by other MCP clients. All browser action tools (such as browser_navigate, browser_click, etc.) are exposed through the standard MCP protocol.

​
Integration with Lingda Platform

Browser Operator can be integrated with third-party platforms (such as Lingda):

​
Authentication Flow

  1. Third-party backend calls Zeus API to obtain a JWT
  2. JWT is passed to the Browser Operator extension
  3. Extension uses JWT to connect to WebSocket

​
Tool Invocation Flow