Top
Best
New

Posted by D_R_Farrell 4 hours ago

Launch HN: Onlook (YC W25) – An open-source developer tool for designers(github.com)
Hey HN, I'm Daniel, founder of Onlook (https://github.com/onlook-dev/onlook and onlook.com).

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!

57 points | 56 comments
alongbottom 19 minutes ago|
I decided to give it a go and, to be completely honest, this is a great way to kind of wrap an existing site and make edits to it. I like how it will stick to the existing style but also let me tweak things using the inspect tool. Like a real-time figma. Well done guys.
D_R_Farrell 17 minutes ago|
Definitely appreciate that! One thing that I find quite underrated when using the tool is the suggestions that it provides. A lot of times it feels like the tool is anticipating the next thing that I would like to design and I find it to be quite powerful in the process.

Also a hidden feature is holding ALT/Option to measure distances between elements which makes it much easier to understand how something was designed.

p2hari 24 minutes ago||
nice to see this here again. When it first came out I had installed it on my device. I have been receiving updates. But did not look into much as my dev workflow has changed. The last time I tested was also on Astro framework and tanstack start and there were some issues with config set to "server rendering" . Will look into this again.
D_R_Farrell 14 minutes ago|
It's always great to hear from our early users! You're right that we were not able to support Astro at the time. And that was a big point of feedback that we got from a lot of people who had been trying to design with Onlook. We had a pretty tight constraint on only working with Next.js and Tailwind apps with the first version of the editor, but now we act more like a framework agnostic design IDE.
penne_pastaa 40 minutes ago||
Love that every agent edit becomes a normal PR. What happens when parallel variants (say, three pricing-card layouts) touch the same component? Does Onlook help you pick and merge a winner, or is that manual git conflict resolution?
thebrubaker 34 minutes ago|
you can bring the problem back into onlook, and it can work across branches to unify those choices into a new PR, or visualize the options for you right there on the canvas. Just point it back at the three PRs you have a conflict with, and ask it for help (or to show you what you need to know to make a decision)
dvsk 1 hour ago||
Looks cool and I'd love to check it out, but there are a few hiccups even getting into the app.

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

D_R_Farrell 1 hour ago|
hmm that's concerning sorry to hear that's happening.

Did any of the other logins work for you? Appreciate you reporting this!

dvsk 1 hour ago||
I'd rather not use my Github or Google accounts for a tool I'm reviewing in a one-off way. Not wanting to turn your HN thread into a support thread, is there a better place to report these issues?
D_R_Farrell 50 minutes ago||
for sure – contact@onlook.com is good or daniel@onlook.com and we can jam.

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!

husseinhb 1 hour ago||
That's great tool but the issue the design of the AI even if it like that easy to change it fix it what ever they still creating the same template of designs i think they needs a lot of samples that are real from real designers to use them as a source. For example when i was creating my platform about 2 years ago designing it was the most complex part because the AI was making a lot of mistakes in layers and z-index and content appearance and much more. But now a days those issues becomes much more rarely to appears and the big issue in the creativity of each design because each design now a days it looking same. I wonder if in the future you will use real designers designs as a source?
krisodd 48 minutes ago||
Design work with AI is definitely a game of balancing creativity and flexibility with the constraints defined in the design system, and it's been something we've thought a lot about.

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.

thebrubaker 1 hour ago||
ya I think the agents are only as good as the tools and resources you give them, I've run into the same problems you're talking about, and typically I carry around a design register / design guidance package that the agent loads and builds on top of, and that makes a big difference. one of the benefits of being local is being able to plug in your existing flow: experiment and play with different approaches to see what works.

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.

Joshearle1 2 hours ago||
I’ve been doing pretty much all of my design work in Codex lately, from trying out rough ideas to refining the UI in the actual codebase. What does your tool do better than Codex for that workflow? I’m especially curious about what happens after the first draft, when I’m dialing in the layout or trying to make a new screen feel like it belongs in the rest of the app. Is there a concrete example where you’d reach for your tool over Codex?
thebrubaker 1 hour ago|
it depends on what you might be driving in codex, but for me it's just a great well designed canvas experience for the same kind of workflow, and I often jump between being in cc or codex, and being in onlook driving things. I think if you're working on a problem that really benefits from being in a canvas space (seeing many variations side by side, jumping between problems quickly) then you might like it more.

also: onlook connects to the same codex you drive, you'll see the same session when you jump from onlook back into codex

reb 1 hour ago||
Big, big fan of open design tools that run real code! The "iterating on Onlook in Onlook" demo got me :)

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?

D_R_Farrell 18 minutes ago||
We've definitely seen a lot of success from tools that have introduced a native plugin. And so we are definitely going to follow up with our own.

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.

krisodd 1 hour ago||
We'll add a MCP for using Onlook from any agent pretty soon, Codex and Claude plugins would be great additions when we have this in place!
HetengAaronLi 1 hour ago||
Wow this is fire. How do you handle the step after exploring ten versions, when the designer wants “the navigation from version 3, the layout from version 7, and the interactions from version 9”? In a canvas tool that’s mostly copying pieces around, but across worktrees it becomes a code integration problem. Can Onlook help combine those ideas?
D_R_Farrell 1 hour ago|
Appreciate the kind words! The answer is going to sound absurdly simple – hold down SHIFT, select the frames you want, and say exactly what you just said! It's pretty wild what you can do when the AI is looking at the same canvas you are + has the context of everything that was created.

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.

Bnjoroge 2 hours ago||
Awesome! Definitely a much needed tool. How does it compare to paper/pen? I've been preferring the former, since pen has its own format and I prefer not to use it. nit: it was pretty hard to find pricing info. I had to scroll down to the footer to see it. Would recommend adding it to the navbar
D_R_Farrell 2 hours ago|
The key difference for Onlook is that we work on the real running application. Paper and Pen are excellent tools for working on abstractions of what you'd like to ship, but still are constrained in a way that favors the editor experience, not the building experience.

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?

ringstar 1 hour ago|
i use claude design for a lot of design work but it always struggles with keeping new components and designs in style with existing components and designs so i have to spend a lot of time telling it to constantly "use the same design system". how do you guys solve this?
thebrubaker 37 minutes ago||
I personally rely on my claude setup and it's memory feature, and that's what plugs right into onlook. I don't end up repeating myself because those lessons learned across sessions persist. That and having a good base design reference to work from.

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.

D_R_Farrell 27 minutes ago||
that's pretty frustrating and there are a lot of ways we keep designs aligned with your real product

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.

More comments...