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!
There are a lot of features that Cursor offers that we still need to meet parity on, but We do see an opportunity to build an excellent tool for creatives to work in code on an infinite canvas that aligns better to the divergent process of design vs. the convergent process of engineering.
Did you agent also recommend this copy??? Fire it! :)
We also think it's a pretty hilarious idea... maximum agent-discovery.
Onlook will always be code-native and caters to the ways designers will need to work with code specifically, not vectors. That means being local-first, but also flexible for the challenges and diversity of code that will have to continue to be maintained in the future.
Onlook will feel a bit light to start when compared to Figma 1:1 on every feature, but the foundation enables us to focus on the future of designers coding and generating assets with AI, not drawing vectors.
For Onlook our goal is to make everything you do truly 1:1 with no translation layer in between what you see and what will ship. It's a small nuance but makes a big difference in the design process.
They certainly have an impressive product that is quite performant from what I remember.
The onboarding is super fast in Onlook you may be surprised how quickly you can go from starting to designing (which you'll see as a claim on our install page: https://www.onlook.com/install)
Also, as is popular with working on major codebases these days, we see a lot of interest in VMs and/or sandboxes, and there's an opportunity to do that in the canvas, but specialized for the ideas that people cook up quickly in Onlook.
> Onlook runs Claude Code or Codex on your own subscription
this was first thing i looked for in the readme and didn't see it. recommend putting it in there :)
> Bring your own agent. We don't ship our own model. Connect the Claude Code or ChatGPT/Codex account you already have, and that agent does the work inside your project. Plug in more tools through MCP connectors to bring all of the context you need to your creative workflow. Work on multiple design tasks at once across repos and pages.
I hate UI in this LLM world, this could just improve it a little bit.
Congratulations! and I hope the YC experience was worth it.
Yes, it was a bit of a journey – we had our original v1 release, then we went to the web, then built an infinite canvas that worked on top of Storybook, and realized that the v1 users were still using the old product.
The YC experience was truly unlike anything I've ever done. You meet incredibly kind, intelligent, and ambitious people and the YC community has been so generous with support and feedback.
I was surprised to see that YC also does a lot for open-source startups too, with dedicated open-source events and many YC companies offer deals to support OSS.
If you're considering applying to YC, my tips are:
1) do it even if you don't think you're ready. The track record of your applications all feeds into getting you an interview, even if you feel like you're wandering around and experimenting.
2) don't use an LLM to draft your application. They really really value reading your raw thinking.
In any event, thanks for trying v1 – would be keen to hear how you like v2!