Sightmap enrichment
When you have a.sightmap/ directory in your project, live-connect returns a sightmap_upload_url. The Subtext plugin pushes your local Sightmap files to that URL before the first snapshot is taken. From that point on, every snapshot includes five additional properties per matched element: semantic component name, source file path, visibility, interactivity, and bounding box. Memory entries attached to components appear in a [Guide] block at the top of the snapshot, giving your agent immediate contextual understanding without having to read source files.
Capabilities
Connection & Navigation
Open a connection with
live-connect, navigate to any URL with live-view-navigate, manage multiple views with live-view-list, live-view-select, live-view-new, and live-view-close, and resize the viewport with live-view-resize. Close everything cleanly with live-disconnect.Interaction
Drive the page with
live-act-click (by component UID), live-act-hover, live-act-fill (single input or batch), live-act-drag (pixel offset), live-act-upload (file input), live-act-keypress (with optional focus target), and live-act-dialog (accept or dismiss). Gate interactions on state with live-act-wait-for.Inspection
Capture a component-tree snapshot with
live-view-snapshot (element UIDs, no image), take a visual screenshot with live-view-screenshot (optionally clipped to an element), and retrieve CSS selectors, attributes, and classes per component with live-view-inspect.Network & Console
List all captured network requests for a view with
live-net-list and fetch full request details by index with live-net-get. List console messages with live-log-list and retrieve a single message with live-log-get.Device Emulation
Apply a device profile — viewport dimensions plus user agent string — with
live-emulate. Use this to verify responsive layouts and mobile-specific behavior without leaving the hosted browser session.Scripting
Evaluate arbitrary JavaScript in the page context with
live-eval-script. Use this to read application state, trigger events programmatically, or probe values that aren’t exposed through the component tree.Reaching localhost
The tunnel is a lightweight local MCP server — separate from the main Subtext session-review server — that creates a reverse tunnel from the hosted browser to your dev server. Add it to your MCP config alongside your existing Subtext entry:live-tunnel to allocate a connection and get the relay URL, then use that URL instead of localhost when navigating in the live browser.
Getting started
1
Connect
Call
live-connect with a starting URL. The tool returns a connection ID and, if you have a Sightmap configured, a sightmap_upload_url — the plugin uploads your .sightmap/ files automatically before the first snapshot.2
Navigate or interact
Use
live-view-navigate to move to a specific route, or jump straight into interaction with live-act-click, live-act-fill, and the rest of the live-act-* tools. Use live-act-wait-for to block until a selector is visible or the page reaches a load state before proceeding.3
Capture a snapshot or screenshot
Call
live-view-snapshot for a Sightmap-enriched component tree (fast, no image data), or live-view-screenshot for a visual capture. Use live-view-inspect to pull CSS selectors and attributes for specific components when you need to verify styling details.4
Inspect network and console output
Call
live-net-list to see all requests the page made, then live-net-get on any index for full request and response details. Call live-log-list to surface console messages — errors, warnings, and custom log output — that the page emitted during the session.5
Disconnect
Call
live-disconnect when you’re done. This closes the hosted browser and frees all associated resources. Always disconnect at the end of a session — open connections count against your quota.To capture structured, versioned evidence of what the Live Browser found — before/after screenshots, diffs, and logs attached to a permanent record — pair the Live Browser with Proof Docs.