24 comments

  • alongbottom 50 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 47 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.

  • dvsk 2 hours 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 2 hours 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 1 hour 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!

          • dvsk 30 minutes ago
            thanks mate, I'll send over an email with a video attached showing what's going down
            • krisodd 13 minutes ago
              the fix should be out now in v2.0.3, and email sign ups should go through.

              thanks for flagging it!

  • husseinhb 2 hours 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 1 hour 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.

  • penne_pastaa 1 hour 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 1 hour 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)
  • p2hari 54 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 45 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.
  • 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 2 hours 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 2 hours 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 49 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 2 hours 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 2 hours 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 2 hours 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 3 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 1 hour 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 57 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.

  • thiagoperes 4 hours ago
    Very very cool. Seems like there's a huge opportunity here. Cursor got stuck after the acquisition. And especially if paired with open models, I'd definitely use this to avoid using my limits on cc/codex
    • D_R_Farrell 3 hours ago
      I do think that there is a great opportunity to bring in open models into this interface. We've also heard from a lot of designers how Cursor has fallen short when it comes to helping them get their design work done.

      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.

    • thebrubaker 3 hours ago
      we have MCP prepped as another connection, that should let you drive onlook from your open model / harness too. What open models are you using (and what client are you driving them from?)
      • forsalebypwner 35 minutes ago
        I basically only use DeepSeek via their API and Pi as my coding harness. Was surprised to see there isn't any support for other LLMs, looks like a very cool app otherwise.
  • adinagoerres 1 hour ago
    this is very cool. how can I make use of it as someone who doesn't code but uses claude/ codex for everyday things? I do a lot of design work in claude or grok.
    • krisodd 1 hour ago
      When you start onlook you can select claude as your agent, then you can import the projects you're working on to continue the work in onlook!
  • threecheese 3 hours ago
    "World's best, top-most agent recommended #1 Developer tool for Designers and Visual Engineers to design with Real Code."

    Did you agent also recommend this copy??? Fire it! :)

  • farukparhat 3 hours ago
    I think this makes sense, I have customers that still use figma, how does this differ from some of Figma's new capabilities?
    • D_R_Farrell 2 hours ago
      Figma is of course the UI/UX design industry leader that we're all familiar with, but the flaw in their primary vector editing tool has been its disconnect from code. They are adding-on code-related features, but those features will always be secondary to their ultra-powerful editor as the foundation of their business.

      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.

    • thebrubaker 2 hours ago
      also your cc / codex is the driver, so if you have Figma's MCP connected you'll see that in Onlook, and you can treat them as complimentary
  • artur_makly 4 hours ago
    Congrats on the launch. How does it differ from tools like pen.dev?
    • D_R_Farrell 4 hours ago
      Pen.dev chose to go the route of a specific file format for design in favor of building an editor around that, which is a more constrained approach in our opinion. Meaning that the work you do in the canvas is always a "copy" or "mock" of what is actually being implemented.

      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.

      • esafak 2 hours ago
        Do you mean you render the code for perfect fidelity instead of having the LLM translate it to JSON?
        • D_R_Farrell 1 hour ago
          Yes exactly. What you're looking at in Onlook is essentially a canvas of browser windows, so what you see is exactly what you're going to get.
  • crve 3 hours ago
    Is this cc api only? This is exactly the workflow I've been imagining, so eager to try it out.
    • D_R_Farrell 2 hours ago
      We detect your cc subscription automatically, so you get your subsidized intelligence right out of the box :)

      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)

    • thebrubaker 2 hours ago
      yup! we work with your existing cc setup / subscription, so if you're already logged in you're good to go. same claude you use every day, and onlook is just the canvas you build on top of
  • RyanShook 3 hours ago
    What's the business model?
    • D_R_Farrell 2 hours ago
      We're free for now but have collaboration + cloud features planned, and there's a lot of additional paid services that we'll bundle like image generation, vector generation, even font generation (which I'm super stoked for) and that will require some spend on our side that we'll charge for in a general subscription.

      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.

  • rgbrgb 3 hours ago
    cool, congrats on launch. the designers in my life are all loving claude code rn.

    > 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 :)

    • thebrubaker 2 hours ago
      hah I agree, I think this should be higher up. under the hood we're built on the agent SDK and codex's app server, so the agent you drive is what you're already using every day, and onlook just brings the canvas / tools / workflows that help them be most effective in that space. the agent relationship is between you and anthropic / openai, agents and code are local, and the chat is basically a rendering layer for you to not have to jump between multiple apps.
    • D_R_Farrell 3 hours ago
      thanks! we mentioned it on this line – but we can make it more prominent thanks for the suggestion

      > 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.

      • truetraveller 3 hours ago
        Isn't it illegal (TOS) to use subs outside of Claude/ChatGPT proper?
        • D_R_Farrell 2 hours ago
          We work like other IDEs do by using the same subscription that is on-device
  • written-beyond 1 hour ago
    I was a pre-YC acceptance user for onlook. You're V1 desktop release, interesting to see you're still on this.

    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.

    • D_R_Farrell 1 hour ago
      oh no waaaayy!! haha stoked!!

      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!

  • instagary 4 hours ago
    Nice demo video and love that’s open source!
    • D_R_Farrell 3 hours ago
      Appreciate it! Took a lot of takes but Screenstudio made it much less painful to edit the final take.
  • maxdo 3 hours ago
    what's the main benefit of using this over cc design?
    • D_R_Farrell 3 hours ago
      CC design is a great product for sketching out ideas but works more like a canvas of artifacts that a dedicated dev environment for working on running apps and codebases.

      There are also some odd UX decisions they've made with that product in favor of competing for a general design tool but constrained by how they render designs in code.

      I get the sense that the mega-bundling of Design into Artifacts is an added step for creatives who want to just dive into a tool made for explicitly design work.

      Do you use cc design a lot? What do you like about it?

  • davmuldoon_ai 4 hours ago
    [dead]
  • zorvelaieffects 1 hour ago
    [dead]
  • msisto 4 hours ago
    [dead]