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
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.
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.
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.
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?
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.
> 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.
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.
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?
Did you agent also recommend this copy??? Fire it! :)
We also think it's a pretty hilarious idea... maximum agent-discovery.