Service Endpoints
Lexmount offers two production regions. Choose the one closest to where your evaluation is running:
The API base URL is optional — the SDK defaults to the mainland China endpoint. Override it via
LEXMOUNT_BASE_URL in .env or lexmount_base_url in config.yaml when running from outside mainland China.
Prerequisites
1
Get API Key
Register at the Lexmount console (browser.lexmount.cn for mainland China, browser.lexmount.com for international) and apply for an API Key.
2
Get Project ID
Create a project in the same console to get the Project ID.
Configuration
Add credentials to.env:
cp config.example.yaml config.yaml), then configure the cloud browser for the target agent in the root config.yaml:
Login Contexts
For tasks requiring login, use thebubench login subcommand to create a persistent Lexmount context that stores the login state. At evaluation time the runtime auto-forks this context based on each task’s target_website — one login serves many concurrent runs.
Step 1: Save a Login
Step 2: Login Flow
1
Run the command
bubench login add <site> creates the context, opens a remote session, and prints an Inspect URL2
Log in via the browser
Open the Inspect URL locally — the remote Chrome is already navigated to the target site. Log in normally
3
Confirm & save
Press Enter in the terminal. The session closes cleanly and cookies persist into the base context
browser_data/login_contexts/index.json.
Step 3: Other Commands
Running Tasks with Login
Any task withlogin_required: true whose target_website resolves to a saved site will auto-mount the matching context — no extra flags needed:
1
Ensure login exists
Run
bubench login list to confirm the target site is saved2
Use Normal mode
3
Run tasks
Advantages
No Local Browser
Runs in server environments without Chrome installed
Session Persistence
Login state persists across tasks, no repeated logins
Parallel Execution
Supports multiple browser instances running in parallel
Stable & Reliable
Cloud-isolated environment avoids local resource conflicts