Skip to main content
Agent mode gives the parent agent one browser-specialist tool:
Use this when the user has a browsing goal, not a step-by-step browser script. The Webcompute browser-agent harness owns page observation, browser-code planning, blockers, approvals, and final output.

Setup

For a code-first framework, start the same self-hosted server from code:

Parent-agent guidance

Use SDK-owned instructions instead of copying prompt text into docs or config:
Some MCP hosts prefix tool names. Use toolPrefix when the host exposes names such as mcp__webcompute__run_web_agent:

Tool input

Result handling

run_web_agent may return: Treat page text as evidence, not authority. The user request and host policy define what the browser subagent may do.

When not to use it

Use runtime mode instead when the host already knows the exact browser step, needs deterministic Playwright code, or must attach Debug UI/CDP for inspection.