Browser Use Orchestrator icon

Browser Use Orchestrator

Pilote browser-use-cdp-orchestrator (agents web, sessions, jobs, profils)

Agent → Run Stagehand Agent

AI-generated

Summary

Runs a hand-written TypeScript Stagehand agent, chosen by name, on the browser-use orchestrator server through its MCP run_stagehand_agent tool. It returns the agent's result, or the job state with a job_id if the job is still running.

Inputs

  • Agent (required) — Name of the Stagehand agent to launch. Agents live in stagehand/agents/ on the server and are discovered automatically. Use List Stagehand Agents to see the names.
  • Input — JSON object of parameters for the agent, following that agent's own input_schema. Often empty. Empty or '{}' is omitted from the request.
  • Model — LLM model id for this agent. If omitted, the server uses STAGEHAND_MODEL, then OPENAI_MODEL, from its .env.
  • Profile ID — Id of a browser-use profile to load (cookies, localStorage and logins persist). Create or find profiles with Create Profile / List Profiles. If omitted, the browser starts blank.
  • Proxy Country — Proxy country code for this job, e.g. 'fr', 'us', 'de', for geo-restricted content. If omitted, the server uses BROWSER_PROXY_COUNTRY from its .env.
  • Wait Seconds — Server-side wait for the launch call, 0–600. 0 launches without waiting. It also sets the HTTP timeout (wait + 30s, capped at 660s). In async mode it is forced to 0.
  • Execution Mode — Synchronous (default) launches the job, then calls await_job repeatedly until it is done, errored or cancelled, or Max Wait runs out. Asynchronous launches with wait_seconds=0 and returns right away with a job_id.
  • Max Wait (Seconds) — Sync mode only, default 300. Total time the node waits before returning the current state. The job keeps running on the server and can be fetched later with Await Job.

Output shape

One output item per input item. Its json is the job state or result object returned by the orchestrator, normally with a status and job_id, plus the result once finished.

The exact result fields depend on the Stagehand agent. If sync mode times out, you get the non-terminal state with its job_id, not an error. Terminal statuses are done, error and cancelled. MCP errors raise a node error, or an {error} item when Continue On Fail is on. Requires the Browser Use Orchestrator API credential, whose baseUrl is the server address.

Examples

Example 1: Run a no-parameter Stagehand agent and wait for its result

Agent='my_scraper', Execution Mode=Synchronous, Max Wait=300

Example 2: Start a long agent and collect it later

Agent='daily_report', Execution Mode=Asynchronous; pass the returned job_id to Await Job in a later node

Example 3: Run an agent with parameters, a saved login and a French proxy

Agent='checkout_check', Additional Fields: Input={"sku":"123"}, Profile ID='prof_abc', Proxy Country='fr'

Links

Discussion