Glossary - Webcompute

Browser infrastructure

The managed browser layer that lets AI agents browse, inspect, debug, and return artifacts from the web.

A Webcompute-created headed browser runtime with lifecycle, status, resources, Debug UI, CDP, and optional recording.

The ways an application or agent operates a browser: SDK, CLI, MCP, REST, CDP, and browser-code execution.

Bounded page evidence returned after browser-code execution. Used by agents and humans to decide the next step.

A generated file, screenshot, recording segment, or downloaded file associated with browser work.

A signed live inspection URL for a managed browser.

Chrome DevTools Protocol. Used by external frameworks and protocol clients to attach to a browser.

Model Context Protocol. Webcompute exposes browser tools to coding-agent hosts through local MCP configuration.

The optional model-backed Webcompute layer that delegates a whole browsing goal to a configured model.

The deterministic control surface for running focused Playwright-backed code against the active page of a managed browser.