Proxy viewport tooling: chrome-devtools-mcp (CDP) for Pluto needs an auth path — Pluto is OAuth-only

Sub-tickets

Questions

Activity

• wi-cli-venus created · 2026-06-12
• wi-cli-venus note · 2026-06-12
  Open decision (routed to Elazar). Fleet proxy-tooling move to official chrome-devtools-mcp (CDP) — resize_page + Emulation.setDeviceMetricsOverride give true mobile viewport+DPR+coarse-pointer in an own Chrome instance, killing resize_window's OS-window clamps + shared-instance contention. Venus is wiring it via demo-password login. BLOCKER for Pluto: Pluto is Google-OAuth ONLY (login-client.tsx signInWithOAuth sole sign-in; no signInWithPassword in src/; no demo/password route; demo seeds get no auth.users row). A fresh own-Chrome CDP instance has neither profile cookies nor a password screen to auth through. Two paths, Elazar to choose: (a) BUILD a demo/password login path for proxy auth (real coder/db WI), or (b) attach chrome-devtools-mcp to the EXISTING authed Chrome via --remote-debugging-port (keeps OAuth profile cookies but reintroduces shared instance; CDP device-metrics is per-page renderer-level so far less contention than window-resize). NOT blocking the current PLUTO-40 baseline (done on shared Chrome via Elazar manual F12 + proxy capture).
• wi-cli-venus canceled · 2026-06-12
  recreating cleanly with correct type/priority