Wonder Dev View

Wonder Dev View is an IDE for engineers who care about design, built by Wonder and introduced by co-founder and CTO Boris. It is a development environment that combines multiple Claude Code and Codex accounts, each on its own subscription, with an editable design canvas that sits right beside your code and the running app. Wonder starts with the repository you already have: you can connect GitHub or open a local project, and agents work on your machine with your team's components, conventions and tools. Its stated purpose is to be a place to shape an idea, make it work and get it into someone's hands, giving engineers more room to use their own judgment. The product responds directly to how coding agents have changed development. In the launch letter, Boris writes that agents changed how much we can build, not how much we need to understand it, and that he wanted a development tool that keeps him close to what he is making. Two things he wanted in his own IDE shaped Wonder: multiple Claude Code and Codex accounts, each on its own subscription, and an editable design canvas right beside his code and running app. He describes wanting the design loop to feel ordinary, with fewer explanations about which button you meant and more time getting the button right. The underlying stance stated on the site is that good software still needs your judgment, and that a working result is where review begins. Wonder organises work around parallel worktrees. Each task gets its own worktree, with its chats, changes, terminal and pull request together in one place, so you can explore a feature while another agent fixes a bug, or start from an existing branch. For code-only work you can stay in the full-screen coding view. On the accounts side, you can connect several Claude Code and Codex accounts, each on its own subscription, pick the account, model and effort for each chat, and optionally let both agents share saved memory. The site notes that your agent subscriptions stay separate, so multiple accounts remain distinct rather than pooled. Context and autonomy are both configurable. You can give the agent the context you would give a teammate: a file, a design, a related chat or another worktree. You then choose how much it does on its own, from asking first to letting it run. In the walkthrough shown on the site, an agent given the instruction to redesign the pricing page reads the current plans and pricing table, edits the pricing table and plans files, searches for the price formatting helper, runs the pricing tests, reports that plans now carry a yearly price, and then continues with a monthly and annual toggle plus a Save 20% badge — with a note to ask Codex to review it when done. The design canvas is the second pillar. You can attach a screen from your designer and ask the agent to build it in your repo with your existing components, or bring a screen from the repo onto the canvas and work out the details visually. You can then run the app beside the design. Selecting an element in the Preview adds it to the chat so the agent knows exactly what you mean, and you can also capture an element onto the canvas, change it there and take it back to the repo. The stated aim is that this loop feels ordinary: fewer explanations about which button you meant, and more time getting the button right. Review and shipping are built into the same surface. Because a working result is where review begins, you read the diff, run your checks and can let Codex review Claude's code, or the other way around, while you still decide what is ready. From there you open the pull request, mark it ready, address feedback or fix failing checks, with the status shown right beside the changes — the walkthrough shows a draft pull request with the changed files, a Checks panel and a View on GitHub action. On Pro you can publish the app's Preview to a link someone can open in a browser and send it with the pull request. The canvas is collaborative too, with live editing on Pro, so a designer can shape the interaction while an engineer keeps it grounded in the code. Taken together, the approach is to keep agents, code, design and review in one continuous loop anchored to your own repository. Wonder does not ask you to move your project into a new hosted environment: it connects to GitHub or opens a local project, and agents work on your machine with your team's components, conventions and tools. Each task is isolated in its own worktree with its chats, changes, terminal and pull request together, so parallel agent work stays separated by task rather than tangled in a single working copy. Design context flows in both directions — a designer's screen comes into the repo as a build instruction, or the repo comes onto an editable canvas — and the running app sits beside the design so the element you point at is unambiguous. The stated benefits follow from that loop. Engineers get a development tool that keeps them close to what they are making rather than one step removed from it. Running several agents in parallel, each on its own subscription, lets you explore a feature while another agent fixes a bug. Giving the agent a file, design, chat or worktree as context reduces the back-and-forth about what you meant. Selecting elements in the Preview rather than describing them lowers the ambiguity in design feedback. Letting one model review the diff of another adds a second pass before you decide what is ready, and the pull request, checks and status sit beside the changes so shipping is not a separate context switch. Concrete workflows described on the site include adding a refund button to an order page, where the agent finds the refund logic in the payments service, reuses an existing ConfirmButton so it matches the rest of the page, edits four files and runs a typecheck; redesigning a pricing page with a monthly and annual toggle; exploring a design like a gallery card screen on the canvas; and reviewing a diff where Codex reviews Claude's code before the pull request is marked ready. Another workflow pairs a designer shaping an interaction live on the canvas with an engineer keeping it grounded in the code, and a further one publishes a working Preview link so someone else can try the app and receive it alongside the pull request. Wonder runs on Mac and Windows and is free to start, with downloads offered for macOS. Shared canvas editing and Preview links are on Pro, while your agent subscriptions stay separate. The site lists engineers at Autentic, Deeploi, Arc, Browserbase and CodeRabbit as users. It is aimed at engineers who build with coding agents and care about design, and at teams where designers and engineers work on the same interface. Full documentation for the design features is available in the Wonder docs. The takeaway is that Wonder Dev View is a place to shape an idea, make it work and get it into someone's hands, built on the belief that agents change how much we can build but not how much we need to understand it. By putting multiple Claude Code and Codex accounts, parallel worktrees, an editable design canvas and a running app preview side by side — and closing the loop with cross-agent review and pull requests — it gives engineers more room to use their judgment from the first prompt to the pull request.