Skip to main content
POST
Create Browser Use Run

Authorizations

X-Browser-Use-API-Key
string
header
required

Body

application/json

Start a new browser-use run OR continue a disposable session.

SIMPLER than browsercode: NO workspace concept (shared agent-workspaces are browsercode-only) and NO code. Sending workspaceId is rejected (see the validator) — the capability model is enforced, not silently ignored.

Continuation via session_id (v2 persist-memory). browser-use 409s on a busy session (it does not queue — that's browsercode's behavior).

task
string
required

What you want the agent to do in the browser.

Minimum string length: 1
browser
RunBrowserSettings · object | null

Browser/proxy/screen settings for this run.

sessionId
string<uuid> | null

Continue a disposable session. 409 if that session is currently busy (browser-use does not queue). Omit to start fresh.

model
string | null

Model to run. Omit for the server default.

attachedFileIds
string<uuid>[] | null

Upload ids from POST /agents/browser-use/files to give this run.

Maximum array length: 20

Response

Successful Response

Async run accepted. Poll GET /runs/{id}/status or GET /runs/{id} for progress + result.

id
string
required

Run id, e.g. "run_...".

agent
enum<string>
required

Which agent is running it.

Available options:
browser-use,
browsercode
sessionId
string<uuid>
required

The conversation this run belongs to (new or continued).

status
enum<string>
required

Initial state — 'queued' or 'running'.

Available options:
queued,
running,
completed,
failed,
stopped
workspaceId
string<uuid> | null

The run's workspace, if the agent has one (browsercode). Its files live here.

missingFileIds
string<uuid>[]

Attached upload ids that could not be confirmed in storage at creation. The run still starts.