Installation
bubench run will create the agent venv defined in config.yaml (default .venvs/browser_use) and install the browser-use
extra on first use.
Activate .venv (or use uv run bubench ...) before running bubench commands.
Configuration
Configure browser-use in the rootconfig.yaml under agents.browser-use:
active_model to the profile name you want to use by default, then switch at runtime with --model <name>.
Supported Model Types
Configuration Parameters
Why no
browser_control?browser-use always operates with DOM and vision running in parallel internally — there is no separate “DOM-only” or “vision-only” mode to expose. use_vision only controls whether screenshots are included in the LLM’s context; the underlying interaction strategy is fixed by the framework itself.Browser Modes
Local Browser: Use local Chrome, suitable for development and debugging. No extra parameters required.LEXMOUNT_API_KEY / LEXMOUNT_PROJECT_ID in .env, then reference them under browser in config.yaml:
AGENTBAY_API_KEY in .env, then reference it under browser in config.yaml:
- AgentBay SDK is treated as an optional dependency. Missing packages or incompatible exports fail only when
browser_id: agentbay; other browser modes continue to work. - Session cleanup failures in AgentBay backend are logged and do not mask task execution errors.
Usage Examples
Basic Run
Run Specific Tasks
Evaluation
Supported Benchmarks
- ✅ LexBench-Browser
- ✅ Online-Mind2Web
- ✅ BrowseComp