New here? Close Settings to try fallback, or pair VT Code below. Press ? after closing this dialog for the quick guide. The paired VT Code TUI remains the source of truth for workspace, policy, pairing, and writes.
- Connection
- In-memory fallback
- Workspace
- Browser memory
- Browser origin
- http://localhost:5173
- Runtime
- Fallback
- Pairing lease
- 300 seconds
- Bridge limits
- 1 MiB · 8 in flight
- Listener
- Browser only
No bridge is paired. Browser edits stay in memory and never touch the filesystem.
Connect or re-pair a VT Code bridgeTwo-step pairing #
1 Start in the VT Code TUI
For **VT CODE TURN**, run this in the same interactive session:
`/webmcp pair http://localhost:5173`
VT Code prints a WebSocket URL and a one-time pairing code. 2 Paste into this web app Copy both values from that same running VT Code session, then pair below.
Keep the TUI running while the browser is connected.
Workspace only? Start vtcode webmcp serve
instead. It does not provide VT CODE TURN.
Nothing is written by the browser. The code and session token stay in browser memory. VT Code remains the approval authority.
Choose a workspace and setup modeTerminal-assisted #
Choose the workspace from this page The browser cannot launch VT Code or grant filesystem access. Enter a path, copy one setup command, run it in a terminal, then pair here.
ACTIVE SESSION · VT CODE TURN
Open with the VT Code agent #
Starts VT Code in the selected workspace. Then run the shown /webmcp pair
command in its TUI.
WORKSPACE ONLY
Open for editing #
Starts the headless bridge for workspace inspection and proposals. It does not provide VT CODE TURN.
After the terminal prints the URL and one-time code, paste both values above.