Dedicated pages for the surfaces Scout exposes publicly
Scout exposes two kinds of surfaces: runtime surfaces where an agent executes work (browser, canvas, extension, payment) and platform adapters for a specific application (Figma). Each surface gets a dedicated page so the agent only receives the tools the workflow actually needs.
Surfaces directory
Runtime surfaces are where an agent executes work. Platform adapters expose a specific application's capabilities.
Runtime surfaces
Where an agent executes work.
Browser
Scout's browser runtime is the broadest public surface: one hosted environment for clean browser sessions, CDP-backed automation, canvas and WebGL inspection, commerce flows, and multi-step web workflows.
Navigation, extraction, screenshots, forms, downloads, cookies, and network-aware automation.
Canvas
Canvas is the connector for rendered surfaces that break normal DOM assumptions: frame diffs, WebGL state, and interaction sequences across canvas-based interfaces.
Canvas-heavy apps where DOM-level browser tools are not enough.
Extension
NewExtension is Scout's connector for sideloading and automating unpacked Chrome extensions: launch, background workers, storage, and reload loops for development workflows.
Sideloading and automating an unpacked Chrome extension during development.
Payment
Payment is Scout's commerce connector: a dedicated surface for balances, challenge flows, payment execution, and money-moving workflows.
Balance checks, commerce flows, challenge handling, and payment execution.
Platform adapters
A specific application, paired through its own runtime.
Figma
Scout's Figma connector pairs with a plugin-backed runtime so agents can inspect and mutate live files, components, variables, and exports through MCP.
Working against a live Figma file instead of static exports or screenshots.