Browser-native AI agents vs IDE-first: Windsurf, Frontman, and DevTools MCP
AI coding agents are moving from IDE add‑ons to browser‑native workflows, offering new tradeoffs in speed, context, and security for engineering teams. [Frontman](https://frontman.sh/vs/windsurf/) is an open-source, browser-native agent that integrates as a plugin for Next.js, Astro, and Vite, serves an overlay at /frontman, and edits real source files with hot reload. Its browser-side MCP server gives the agent live DOM, computed CSS, screenshots, and click-to-select element context. [Windsurf](https://frontman.sh/vs/windsurf/) is a proprietary VS Code fork with the Cascade agent, strong autocomplete, a preview panel, terminal integration, and large-scale refactors. The PlayCode “alternative” pitch targets a different user; [PlayCode](https://playcode.io/windsurf-alternative) builds whole sites from plain English in the browser and is aimed at non-developers. Google’s [Chrome DevTools MCP](https://github.com/ChromeDevTools/chrome-devtools-mcp) exposes a live Chrome to agents (Gemini, Claude, Cursor, Copilot) via MCP, enabling traces, network analysis, screenshots, and reliable automation through Puppeteer. It brings security considerations too, since the browser state is exposed to the MCP client and some performance tooling may hit the CrUX API.