Agent Browsers

Give an agent its own fresh browser for a project and the sites you choose. In Settings → Agent Browsers, an organization admin grants a key a project, exact site origins and an expiry. View session previews and use Stop session to end a lease. Organization and platform kill switches are available; the capability defaults on and agent grants remain explicit.

This branch proves real local Chromium sessions, screenshots and Stop. Production deployment and acceptance are pending. A running GoodQA browser worker is a deployment prerequisite (agent-browsers-worker in the capability registry describes that process, not an environment variable). Each organization and agent key sees only its authorized sessions and artifacts.

Agents connect through the existing remote MCP server. Start with agent_browser_open, poll agent_browser_status, navigate and interact, take a screenshot, then agent_browser_close. Browser text is untrusted page content. Use existing vault references for password delivery; afterward agent reads and previews are withheld. Existing paired-machine consent handles the person's real browser.

• API reference: /v1/openapi.json, agent-browsers tag; REST /v1/orgs/{orgId}/agent-browsers.
• MCP tools: parameters and examples, registration and gates.
• Runbook: local acceptance and DigitalOcean worker setup.

The technical guide records TTL, action and artifact bounds, credential handling, local commands and production acceptance prerequisites.