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