Flagship features · CDP browser mirror WebView2 CDP

CDP browser mirror

When the AI you're chatting with browses the web, every action (navigation·clicks·input) is reflected live in the in-app browser panel beside the terminal. The app's own screen is invisible to the agent, so it's never operated by mistake.

What it does

When you hand an agent a web task, you usually can't see what it opened or where it got stuck. The mirror turns the agent's browser into a real panel on your screen, letting you watch it work in real time as if over its shoulder. The agent drives by looking only at that panel, while the app's own UI is neither visible nor reachable.

Enable

In dev, launching the app with npm run dev:app always turns the mirror on and connects agents automatically (proxy 9522+base). In a release, turn on Settings → Agent browser mirror and restart the app, and agent sessions connect automatically (default port 9422, changeable in settings). While it's on, the status bar shows Mirror :port.

An agent session reads the mirror connection at startup. A session that's already running must be restarted once to attach to the mirror.

Usage

Just say "open ○○ in the browser and check it," and the page the agent opens isn't a floating temporary window but a proper in-app browser tab, with every subsequent navigation·click·input shown live in that panel. When the agent changes pages, your view follows along, and when the work is done you take over that tab as-is.

Limits · caveats

Multi-agent setups are separated per Space. An agent launched from an app terminal drives by looking only at its own Space's panel, and new pages also open in its own Space. That said, agents within the same Space can see each other's panels, and even if you move a terminal tab to another Space it keeps pointing at the old Space until the shell is restarted. New pages open one at a time (opening two at once rejects the second, which can be retried).

Reference