Posted by D_R_Farrell 4 hours ago
Onlook is a desktop app that puts a canvas on top of your real codebase, letting you design directly in code with the agent you already use. Over 25,000 designers and developers have supported the project, 100+ have contributed, and it's been the #1 trending repo in the world twice. We just rebuilt the entire product as an agentic design tool, and open-sourced it to the community.
Here’s a demo video: (https://youtu.be/BogcYWf4siM)
If you're an engineer, traditional engineering tools are largely built for convergence, whereas designers tend to explore and diverge on ideas. Onlook gives designers a familiar canvas while managing all of the dev processes that get between them and making mind-blowing designs in code. Designers can work on a multiple simultaneous worktrees that run on the real app locally, and every change lands as a PR you can review or throw away, so there aren’t mockups to rebuild.
We built Onlook because we believe there needs to be a developer tool that works the way designers do.
More and more, designers are expected to work in code. Designers think by seeing, drafting, arranging variations, using references, and remixing ideas. That’s why the canvas has been the signature feature of design tools because it genuinely is useful for how messy the creative process is. Most of the challenge of using engineering tools for design work is that the first half of starting a project often takes mental bandwidth in of itself (What branch am I on? What page was that last exploration on?) and the second half is constrained by configuring your coded design to present itself (prompting design tools on top of what you’ve built or making temporary navigation for that specific state).
Some of you may remember our earlier Show HNs (July 2024: https://news.ycombinator.com/item?id=40904862, August 2024: https://news.ycombinator.com/item?id=41390449, May 2025: https://news.ycombinator.com/item?id=44127653). Since then, we built a web version (too early), then a Storybook-native build (a mistake). We noticed that our desktop product from July 2024 was still getting hundreds of downloads a month despite zero promotion, so we decided to rebuild it for the new era of designers working in code.
How it works…
Onlook shines at exploring tons of ideas at once. Ask it to lay out every flow in your product, show every state of a component, or riff on ten versions of one screen. Your designs all show up side by side on an infinite canvas, with each frame as a real webview running your actual app with real data. Not as a mockup, but the real deal.
When we built this editor, we had an epiphany that it could be a new kind of IDE for design. Design tools used to be limited to a proprietary setup or closed schema, but now you can push and pull the medium of code to get whatever result you want, so why not give agents an infinite canvas of browsers and see what they do? It turns out, the agents can figure out how to better present coded work by adjusting the urls of browser frames and arranging and resizing them on the canvas.
The concept is simple, but it requires a lot of product thinking. For example, because all of the frames on the canvas share a single browser session, and Chromium only allows six connections per host per session, ten frames of the same app end up fighting over limited connections. So, we had to plan around that, and there are still tons of things we need to do to make the canvas ultra performant.
Onlook is an Electron app where you can import a repo from GitHub or upload a local folder. Then, Onlook creates a git worktree, starts your dev server, and has the agent sort out missing dependencies or other requirements. You never open a terminal and everything the agent does is a normal git diff that can go to GitHub as a PR. We inject a small script into each frame that draws selection outlines and reads the page, so that way you can click an element, say "make this a card layout," and the agent knows exactly what "this" is.
This time we didn't build our own agent. Onlook runs Claude Code or Codex on your own subscription, and we turn whatever the agent emits into one typed event log and draw the UI from that in our own chat interface. On top of that we give the agent a bespoke set of design-specific tools, from arranging frames on the canvas, to making suggestions, to generating multiple iterations of a selection – which is especially useful because the agent decides how to get the app into a state that you need based on your prompt.
We also have our own Artifacts which are quick HTML sketches that live in the editor, but outside your repo. They’re almost like components in other design tools in that they can be carried and edited across every project but are detached from the project with no network access. As an example, you can ask the agent to turn your interface into an Artifact, and use it as a reference for another exploration, or download it as HTML and send it to a coworker as an interactive export of something you have in progress. I frequently go back to the artifacts I’ve made as visual snippets when I need new ideas or need to borrow something that’s already been built.
The desktop editor is free (you can download it from our website at onlook.com) and open source under Apache-2.0, and we'll eventually offer a paid cloud product for teams.
We'd love to hear which repos work and which don't, what you try to do on the canvas, and what's missing. We’re so excited for this to be a new way for designers to work in code!
The Onlook team (Joel - thebrubaker and Kris - krisodd), and I will be here all day!
Also a hidden feature is holding ALT/Option to measure distances between elements which makes it much easier to understand how something was designed.
1. It's not entirely clear from the on-boarding as to why I need an account 2. When trying to setup an account via email I keep getting hung screens or the error: Can‘t verify the user is human. Please try again.
This is on macOS 27.2.1
Did any of the other logins work for you? Appreciate you reporting this!
Kris and Joel just went and diagnosed what was going on with it and it seems like the email window blocked Cloudflare's bot check, so email sign-up was struggling.
There should be a fix landing in about 30 minutes, so definitely give it a try then and email me if you're still having issues!
Onlook lets you add browsers and images to your projects to be used as context, so it's already a strong tool for working with design references
Another way we're addressing this is by keeping the projects you're working on separate from the self contained design artifacts you may generate in the process. Since these can be easily used across projects we find that it's very low friction to take a cool but discarded thing you sketched once and repurpose it for another project where it may fit in better.
cloud platforms / walled gardens are sometimes annoying for that reason, you might have a workflow that works but the platform doesn't support it yet. I prefer to work where I can experiment the most given how rapidly things change.
also: onlook connects to the same codex you drive, you'll see the same session when you jump from onlook back into codex
I'm finding myself spending most of my time inside frontier labs' desktop apps lately and I'm always looking for ways to pull more of my workflow into them... any chance you guys are working on a Codex/Claude Code plugin so I can run Onlook there?
One thing that is a bit different about how Onlook is built versus other design tools is that we are local first. And a core part of that is allowing agents to be run locally, but also to allow agents to design on top of real codebases. So before we do a plugin, we are looking into making it easier for codebases to be put up in the cloud.
I definitely want us to build a plugin though. It does seem like a lot of designers are moving their workflows into the frontier labs desktop apps and we want to make sure that we can accommodate people's preferences for how they like to design.
We do need to do a bit better of a job of persisting project iterations after the handoff is made though. A lot of design work relies on being able to reference past explorations, and the agents tend to lean on cleaning EVERYTHING up that isn't going to be made in the PR, so a lot of times project explorations can be swept up in preparation for an idea going live. But it's a challenge we're definitely able to solve with some tuning and UX.
This is totally ok in our opinion – you want to choose the right tool for the job – we just think the job for designers is trending towards being right up against the real medium of code and how it gets represented when it ships.
Your point on the proprietary format is a good one. There are so many ways to build a design tool, and it felt like agents give us an opportunity to make an entirely new way to craft designs that doesn't require a strict format. Why can't we just select the thing we want to change and do it, regardless of what it is?
Also the agent in onlook is very visually aware and capable, it's constantly verifying work and sees exactly what you see, so I've rarely seen it diverge from the existing components or screens you have up. give it a try and see if it feels more aligned than you get in something like claude design.
When you work in Onlook you work on top of the real codebase, so whether you're starting a project to make a real edit on the running app, or you're just starting a project to make prototypes or sketches off of the foundational codebase, you are pointing the agent to the real code.
Think of Onlook more along the lines of working on top of code and apps rather than just flat HTML/CSS (like what Claude design does). It gives you more power because if you wanted to, you can actually reference a specific part of your repo and build with real React components.
If you set up your codebase to have a design system, you can start every ideation exercise as a new project in Onlook from that repo.