Skip to main content
If you’re running Browser Use Cloud today, switching to pre.dev Browser Agents is an SDK swap + an env-var rename. Same task shape (URL + instruction + schema), same structured JSON out. On our public benchmark (June 2026 run), pre.dev passes 100/100 vs Browser Use Cloud’s 93/100 — and is ~2.8× cheaper and ~4× faster (0.0143vs0.0143 vs 0.0405 per task, 7.9s vs 32.0s avg).

1. Swap env vars + install the SDK

Grab your pre.dev key at pre.dev/projects/key.

2. Run one task

Before — Browser Use
After — pre.dev
Key differences:
  • URL is a first-class field, not embedded in the instruction. The agent navigates there before running.
  • Output schema is JSON Schema, not a serialized Pydantic/Zod model. The runner validates the response and retries on schema-failure.
  • Tasks is always an array — one method covers 1 task or 1,000.

3. Run many tasks in parallel

Browser Use makes you fire N concurrent run() calls yourself. pre.dev takes an array and fans out server-side — one request, one response.
Before — Browser Use (manual fan-out)
After — pre.dev (one call, server-side concurrency)
Up to 1,000 tasks per request. See Run a Task for the full schema.

4. Async + poll pattern

If you were polling Browser Use by session id, pre.dev has a direct equivalent: pass async: true on submit, then call getBrowserAgent(id).
Before — Browser Use
After — pre.dev
See Task Status for the full polling contract (pass includeEvents=True for the per-step timeline).

One-shot Claude Code prompt

Drop this into Claude Code at the root of your repo. Works for any stack — Node, Bun, Deno, Python, monorepos.

Next