Integrations / Browser Use
Launch and agentsExperimental
Run browser-use tasks on Badgr: setup guide
A guide for running a browser-use agent as a finite job with a headless browser. This is not a one-click path.
A setup guide only. Badgr has not tested this path, so expect to adjust it.
Why use Badgr for Browser Use
- Badgr interface
- Launch
- Where Browser Use fits
- Browser agent runtime
- Why Badgr
- Remote browser tasks
- Run a long browser task on an isolated machine instead of keeping a laptop open.
- Screenshots and traces come back as files, so you can see what the agent did.
- A cost cap bounds each run. Badgr has not tested this path, so start with a small one.
What you can do
- Run a web task that takes longer than you want to keep a laptop open
- Collect screenshots as evidence of what the agent did
- Run many browser tasks as separate capped jobs
Quickstart: Run your own script as a job
badgr launch . --max-cost 1 --image <your-image-with-chromium> -- python agent.py
How it works
- 1.You give Badgr your project and an image with a browser
- 2.The script runs headless on an isolated machine
- 3.The agent saves screenshots and traces to the output folder
- 4.You download them with badgr artifacts <id>
What you get
- Screenshots and traces your script saves
- Logs and a receipt
Requirements
- The Badgr CLI installed and logged in (npm install -g badgr-cli)
- A funded Badgr balance
- A Python script using browser-use and a headless Chromium
- A model credential for the agent
- A runner image that includes the browser, since the default image is Python only
What it costs
- The job bills for run time and is bounded by --max-cost.
- Your model provider bills tokens separately.
- This path has not been tested by Badgr, so confirm costs with a small first run.
See pricing for how billing works.
Proof
No tested run is recorded for this integration yet. A receipt and example output will be added here after a real run, not before.
Troubleshooting
Browser fails to start
The default image has no browser. Use an image with Chromium and its system libraries, and run headless.
No screenshots returned
Save them to the job's output folder before the script exits.
Sites block the agent
Some sites block automated traffic from cloud machines. Test with a site you control first.
Developer reference
Ready to start with Browser Use?
Every run or service has a spending limit you set before it starts.