Module browser 

Provider-independent browser capability owned by Supercode.

Supercode owns the operation names, schemas, CLI/MCP projections and policy boundary. A browser product such as Vibewaiting implements the versioned provider wire out of process; it never becomes the canonical agent API. Providers advertise honest fidelity and receive only structured locator/action payloads — arbitrary JavaScript is not part of this contract.

Structs

BrowserOperationDefinition

One operation in the canonical browser registry.

Constants

BROWSER_OPERATION_PROTOCOL

Structured operation envelope version sent to providers.

BROWSER_PROVIDER_MAX_REQUEST_BYTES

Bound for one provider request, including locator values and fill text.

BROWSER_PROVIDER_MAX_RESPONSE_BYTES

Bound for one provider result. Accessibility snapshots are much smaller, but this leaves room for future bounded image/artifact references.

BROWSER_PROVIDER_PROTOCOL

Provider discovery and socket protocol version.

BROWSER_PROVIDER_TIMEOUT

End-to-end provider call timeout.

Functions

browser_operation

Resolve a registry entry by canonical or CLI name.

browser_operation_registry

Return the authoritative operation registry in stable order.

browser_provider_directory

Directory in which out-of-process browser providers publish owner-only discovery records. This follows Supercode’s user configuration root, never a project-controlled directory.

call_browser_operation

Call the first reachable provider for workspace. Transport and availability failures are returned as the same structured outcome shape providers use, so CLI/SDK/MCP all observe identical semantics.

register_browser_tools

Register every canonical browser operation into an existing tool registry. MCP calls this directly; optional agent surfaces can reuse it without letting providers add or remove operations.