Browser capabilities#

Browser automation for an Agent must be supplied through a declared function or MCP tool and enforced by the deployment's fixed capability policy. Creating a standard Session does not inject browser tools or grant browser authority.

The Playwright MCP example supplies a pinned, optional browser provider through the environment's standard MCP transport. Its declared tools support navigation, typing, clicking, snapshots and screenshots. The execution image must contain the provider and Chromium before use.

The Session console displays saved messages, tool activity, function-result requests and artifacts; it does not provide a browser-control pane.

Applications expose browser capabilities through declared tools and must implement their declared interface and preserve ownership, bounded operations, network enforcement and separation from host credentials.

Browser screenshots or recordings produced in a managed environment can become Session Artifacts when saved beneath /workspace/outputs. Use durable files for retention and sharing work for explicit publication.