browser-debugginglisted

# Browser Debugging Skill Drive a real (headless) Chromium against the running NXTG-Forge dashboard from inside Claude Code, using the **Playwright MCP** server. No Windows Chrome dependency — Playwright launches its own headless Chromium inside WSL. ## Where the tools come from (read first) The Playwright MCP server is registered in **`forge-ui/.mcp.json`**, NOT in the plugin's `.mcp.json` (which only registers governance / orchestrator / semgrep). The `browser_*` tools only exist when a Claude Code session has `forge-ui/.mcp.json` loaded — i.e. you are working in the `forge-ui/` repo. From the plugin repo alone they are unavailable. Config as shipped: ```jsonc "playwright": { "command": "npx", "args": ["@playwright/mcp@latest", "--headless", "--console-level", "debug"] } ``` Two consequences of that exact config: - `--console-level debug` → `browser_console_messages` returns **verbose debug logs**, not just errors. Filter for `error`/`warning` yourself; do not assume a clean-looking tail means no errors. - **No `--caps`** flag → the `pdf`, `vision` (coordinate clicks/screenshots), and `devtools` capabilities are OFF. `browser_pdf_save` and coordinate-based interaction are not available here. ## Prerequisites Start both servers from `forge-ui/` (one command starts Vite :5050 + Express API :5051): ```bash cd forge-ui && npm run dev ``` Confirm they're up before driving the browser: ```bash curl -sf http://localhost:5050 >/dev/null && echo "UI up" curl -sf http:/