The Dream of a True Visual IDE
For years, developers have chased the holy grail: a tool that combines the intuitive, visual manipulation of a design app like Figma with the power and flexibility of a real code editor. We've seen countless attempts, from WYSIWYG editors that produce messy code to design-to-code plugins that only get you 80% of the way there. Onlook is the latest, and one of the most ambitious, contenders in this space, aiming to be a 'visual-first code editor' built for the modern, AI-native web.
Its proposition is simple and powerful: point it at a Next.js and Tailwind CSS project, and it spins up a live, editable preview. You can click on any element—a button, a div, a text block—and modify its styles using a familiar, Figma-like toolbar. You can drag to re-arrange elements or even draw new ones directly onto the page. Crucially, every visual change is instantly and cleanly translated back into your JSX and CSS code. It's not a one-way export; it's a two-way, real-time sync. This core concept, if executed perfectly, is a game-changer for rapid prototyping and component development.
AI at the Core
What sets Onlook apart from older visual editors is its deep integration of AI. It features a chat interface that has full access to your codebase. You can ask it to perform complex tasks like 'create a three-column pricing page with a toggle for annual billing' or 'refactor this card component to use a different layout on mobile.' The AI doesn't just spit out code snippets; it understands the project's structure and can create or modify files directly. The architecture diagram in the README reveals how this works: the AI acts as an agent with tools to read, index, and edit the code running in a sandboxed web container. This is a far more robust approach than a simple ChatGPT plugin for your IDE.
The project also gestures towards more advanced AI capabilities, like using images as design references and setting up 'MCPs' (Model Context Protocols), suggesting a forward-thinking vision for how AI can be a collaborative partner in the design and development process.
Strengths and Standout Features
Onlook's greatest strength is its laser focus on the Next.js and Tailwind CSS stack. While a limitation, this specialization allows for a deeply integrated and (theoretically) seamless experience. It understands Tailwind utility classes, Next.js page routing, and React component structure out of the box. Features like component detection, which can identify reusable elements in your project, and branching, for experimenting with design changes in isolation, are thoughtfully included.
The ability to self-host is another massive advantage. Competing services like v0.dev are closed-source and cloud-based, but Onlook gives you the option to run the entire environment yourself. This is a critical feature for companies with strict data privacy policies or those who want to avoid vendor lock-in. The tech stack is also impressively modern, built on Bun, Next.js, and Supabase, which will appeal to developers who like to stay on the cutting edge.
The Harsh Reality of 'Early Access'
Despite the exciting vision, the reality of the Onlook open-source project is sobering. A look at the GitHub repository reveals a project that appears to be stalled. The last release, v0.2.32, was in July 2025—over a year ago as of this review. With 374 open issues, it's clear that maintenance has not kept pace with user feedback. The project's README itself is a testament to its unfinished state, with many key features still unchecked, including a drag-and-drop component panel, team collaboration comments, and support for non-Next.js/Tailwind projects.
This lack of activity is a major red flag. It suggests that the open-source repository may be serving primarily as a lead generation tool for the commercial, hosted version of Onlook, which is promoted via a waitlist. While this is a common strategy, potential users of the open-source version should be aware that they are likely using a deprioritized, and potentially unsupported, piece of software.
The architecture, while powerful, is also a potential source of fragility. The chain of a web container, an iFrame, code instrumentation, and a separate editor UI has many points of failure. For self-hosters, debugging an issue within this complex system could be a significant undertaking, and with a seemingly inactive development team, you'd largely be on your own.
Final Verdict: An Idea Ahead of its Implementation
Onlook is an exciting project that showcases what the future of front-end development could look like. It's a beautifully designed tool with a brilliant core idea. For a solo developer or a small team looking to rapidly prototype a new idea on Next.js and Tailwind, it can be a fun and powerful tool for experimentation. However, it is not a mature or reliable platform. The stalled development, high number of open issues, and long list of incomplete features make it impossible to recommend for any serious production work. It's a project to watch, but not one to adopt—at least not until the open-source version gets the sustained attention it needs to fulfill its incredible potential.