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
- Visit the Chrome Web Store
- Search for “Zeus Browser Operator”
- Click “Add to Chrome”
- Confirm installation
Developer Mode Installation
- Download the extension source code
- Open
chrome://extensions - Enable “Developer mode”
- Click “Load unpacked”
- 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
- Click the extension icon
- Log in to your Zeus account (or scan QR code to log in)
- Authorize extension access
3. Establish Connection
Supported Actions
Navigation
Element Interaction
Page Actions
Advanced Actions
Element References (ref)
Browser Operator uses element references (refs) to identify page elements.Getting a ref
Usebrowser_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 asbrowser_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
Web Data Extraction
Automated Testing
Troubleshooting
Extension Shows “Not Connected”
- Check if you’re logged in
- Refresh the extension (click refresh on chrome://extensions)
- Check if the WebSocket server is running
- Check browser console for errors
Action Execution Failed
- Ensure the page has fully loaded
- Check if the element ref is valid
- Try using
browser_snapshotto refresh the element list - Check if a popup is blocking the action
Blank Screenshot
- Wait for page rendering to complete
- Check for iframe content
- Try using
fullPage: falseparameter
MCP Server
Browser Operator also runs as an MCP server and can be invoked by other MCP clients. All browser action tools (such asbrowser_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
- Third-party backend calls Zeus API to obtain a JWT
- JWT is passed to the Browser Operator extension
- Extension uses JWT to connect to WebSocket