Browser Pair — Collaborative UI Session

Open a headed Chromium browser the user can see, then drive it interactively. The user watches, gives visual feedback, you make code changes and verify live. This is pair programming for UI.

Key difference from /browser-test: This is interactive and headed. You wait for user direction between actions. You edit code when they spot issues, then refresh to verify.

Setup

Parse $ARGUMENTS for:

• URL or port (optional): full URL or just a port number (e.g. 5560 becomes http://localhost:5560)
• Page (optional): where to navigate after login (e.g. "agents page", "run plans")

If not provided, check for .dev-port file or ask the user.

Tools

Use only mcp__playwright-headed__* tools. Never use mcp__playwright__* (headless). The user must see the browser.