> ## Documentation Index
> Fetch the complete documentation index at: https://browser-mcp.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Live view

> Optional view-only native browser streaming and its limits.

Live view is off by default and requires the browser owner's local opt-in. A remote viewer cannot enable it or undo a local pause. The runtime must advertise live-view capability; otherwise the dashboard reports it unsupported rather than pretending to stream.

Open **Watch** from the dashboard, or use `browser_watch` in an MCP Apps-capable client. View-only short-lived tickets are redeemed in the viewer socket's first message, never in a URL. Stop ends the stream for all viewers. Streaming uses a separate bounded media path, not the command connection.

Pixels can expose anything visible in the tab: **they are not password-masked or universally redacted**. TLS does not hide them from the server operator. The relay does not record frames, but viewers can capture them. The overlay shows pointer/actions, not typed text; that does not conceal text appearing in the page.

The viewer distinguishes offline, unsupported, waiting for local opt-in, blocked page, hidden tab, waiting for frame, streaming and stopped states. Connected alone does not prove a drawable frame arrived. Document/tab changes discard stale frames and overlays. Protocol v2 media uses opaque runtime tab IDs, not numeric Chrome IDs.

Server/runtime reconnect requests a fresh stream and ticket; it does not resume missed pixels or replay browser actions. Exactly one server replica is supported. Only authorized ordinary pages can stream; control-plane and privileged-origin protections remain in force.

See [native controls](/native-cli) to enable live view locally, and [security](/security) before sharing a tab.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.