run_web_agent.
Technical default: web mcp run exposes runtime tools for model-free browser
control.
Surfaces
--agent is not a supported shorthand. Use
--surface agent --model <profile>.
Setup and config commands
Important setup flags:
Important run flags:
Generated host configs prefer visible args:
Instructions and prompts
Server-level MCP initialize instructions are absent or tiny to avoid prompt pollution. Use one of these explicit prompt surfaces instead:
The read-only resource
webcompute://instructions/mcp is a small index, not a
large prompt blob.
Application code should use the SDK-owned prompt text:
mcpPrompt() equals mcpPrompt("runtime").
Agent tool: run_web_agent
run_web_agent delegates a whole browsing task to the configured Webcompute
browser-agent harness.
It is exposed only on the agent or all surface. It requires a saved model
profile or direct model environment variables.
Schema
Result
The tool returns:- Text content summarizing the run.
structuredContentcontaining the sanitizedWebAgentResult.isError: truewhen the result status isfailedorcancelled.
needs_confirmation results. Do not ask Webcompute to handle CAPTCHA
through browser code.
Runtime tool: manage_browsers
manage_browsers creates, lists, inspects, stops, resumes, closes, debugs,
connects to, and resolves CAPTCHA blockers for Webcompute browsers.
Schema
Actions:
create, list, get, status, stop, resume, close, debug_url,
cdp_url, captcha_status, captcha_resolve.
Runtime tool: execute_playwright_code
execute_playwright_code runs focused browser code against a Webcompute browser.
The page variable is already in scope and points at the active page.