Using Chrome-devtools-MCP with Polypane (polypane.app)

Polypane now works with chrome-devtools-mcp (the Model Context Protocol implementation that lets coding agents like GitHub Copilot, Gemini, Claude, and Cursor inspect and run code in a live Chromium runtime), enabling AI-assisted agents to inspect and verify changes across Polypane’s multi-view panes. This is significant because it gives coding agents real runtime feedback across multiple viewports simultaneously — speeding up debugging, responsive testing, and validation of generated code. Puppeteer and chrome-devtools-mcp were updated to support Polypane, which also improves support for Electron apps more broadly. Technically, you run Polypane with remote debugging (example: --remote-debugging-port=5858), then start chrome-devtools-mcp pointed at http://127.0.0.1:5858 with the experimentalIncludeAllPages=true flag so the MCP can see each pane. In VS Code you can add an MCP server via a one-line CLI that invokes npx chrome-devtools-mcp with those args. Developers should add a system prompt instructing the agent that multiple panes are views of the same tab (use window.__polypane.title for pane names), to exclude internal Polypane URLs, and to apply actions across panes in parallel. Caveats: LLMs can hallucinate UI elements and can access or mutate live page data, so review any evaluation scripts or actions before granting permission.