🛰️ Bridge

Connecting…

A connected editor agent - via the api mcp_bridge MCP tool - can drive this browser: open and organize tabs, navigate, click, type, scroll, and read reviewed page content. Credential-bearing diagnostics, cookies, storage, network capture, arbitrary scripts, and signed-in provider actions stay local to Vynx. The bridge credential stays hidden; copy it only when pairing a trusted client.

Bridge credential

Configured - hidden

Bridge server

—

Keep automation tabs in background (recommended) Blocks remote tab-activate and focus:true requests. Work remains visible in labeled tab groups, status indicators, and Live activity, but may be less immediately noticeable. Uncheck only when a trusted agent must take keyboard focus; your next keystrokes can land in that tab.

This tab is the MCP Bridge's visible indicator. Closing it won't stop the bridge — it reappears while the bridge is active. Use Stop here (or the extension Options) to end remote control.

📡 Live activity

Every action a connected editor agent runs through this bridge appears here as it happens - latest activity at the top. MCP clients configured with this session share one serialized browser-mutation queue, while each managed client keeps its own sticky target/workspace. Legacy direct clients without workspace metadata share the legacy target. The Browser agent keeps separate run-owned tabs; source badges distinguish clients when available. Use a separate browser profile and session ID only when agents need isolated cookies, storage, or login state.

Waiting for remote commands…

🤖 Browser Agent

The Browser Agent is a separate tool with its own page: you give it a task in plain language and it drives a tab for you. It runs whether or not this bridge is on, and this bridge runs whether or not you use it - they share an underlying dispatcher, with privacy-sensitive actions excluded from remote bridge sessions.

🔬 Diagnostics - build, bridge metrics, activity & optional page evidence

Copy the Compact MCP Bridge Diagnostics Bundle, even when no controlled page is open. It combines build identity, persisted bridge metrics, and this worker's activity with compact get-debug-pack evidence when that page is available. Missing sections are reported explicitly. Sensitive values and fresh quota requests are omitted.