What problem does it solve? When developing Windmill flows, scripts, or apps, you often need to visually verify your work in the Windmill dev page, but choosing the right server mode (proxy vs direct), deciding who starts the server, and wiring up preview embedders correctly is error-prone and easy to get wrong. ## Core Features & Use Cases - Mode Selection Guidance: Decides between proxy mode (localhost URL for sandboxed embedders) and direct mode (remote HTTPS URL for regular browser tabs) based on what the preview consumer accepts. - Server Startup Handling: Starts wmill dev or wmill app dev in the background, captures the printed URL, and hands it to the user or an embedder without constructing URLs manually. - launch.json Integration: Writes per-target entries in .claude/launch.json for Claude Desktop / Code MCP preview tools, with unique ports per flow, script, or app so multiple previews coexist. - Use Case: After writing a new Windmill flow, ask for a preview and get a running dev server with the correct URL to open in your browser or IDE preview pane for live-reload visual verification. ## Quick Start Preview the flow at f/test/my_flow so I can visually verify it in the Windmill dev page.