onlook

onlook-dev/onlook

The Developer Tool for Visual Engineers • An Open-Source AI-First Design tool • Visually build, style, and edit your code with AI • World's best, top-most agent recommended #1 Developer tool for Designers and Visual Engineers to design with Real Code.

Ship status

Still shipping

Pushed in the last 30 days.

Last push
21 Oct 2026
21 days ago
Ship score
51/100
How it is calculated →
Stars, last 7 weeks
Stars, weekly: 26,828 → 27,156 (29 Sep – 10 Nov 2026)
+250 stars in the 28 days to 10 Nov 2026

Shipping: pushed in the last 30 days · slowed: quiet for 31–120 days · silent: no push in over 120 days.

Repo facts

What GitHub reports.

Stars
27.2K
Forks
2.1K
Open issues
382
Watchers
124
Primary language
TypeScript
Created
25 Jun 2024
Owner
onlook-dev · Organization

Open issues are the issues and pull requests GitHub reports as open; watchers are the accounts subscribed to the repository. OSI-approved license — GitHub’s own license field, not legal advice. 212 startups in the directory ship primarily in TypeScript.

Topics

#ai#claude-code#codex#cursor#design#design-system#design-to-code#design-tool#figma#frontend#ide#nextjs#react#supabase#tailwindcss#typescript#ui#vibe-coding#vibecoding#visual-engineering

How it got here

What the classifier decided, and when.

Classified as an open-source startup by Jev, TypeSafe’s classifier, on 22 Sep 2026 — os_startup 99%, self-hostable 29%, hosted offering 53%. The classifier reads only the repository’s name, description and homepage; it can be wrong, and a probability under 0.5 puts a listing in the review queue rather than out of the directory.

Listed since the Sep 2025 crawl. Answered by jev-1.13.0. How the classification works →

Embed your status

Put this badge on your README.

OSSEAN ship status: shipping — last push 21 Oct 2026This is the badge for onlook-dev/onlook, as served from the URL below.
[![OSSEAN: shipping](https://ossean.com/badge/onlook-dev/onlook.svg)](https://ossean.com/onlook-dev/onlook)

Updates daily, from the last push GitHub saw.

Honest caveat: GitHub proxies README images through Camo and rewrites the anchor with rel=“nofollow”, so a README embed sends you referral traffic and brand, not link equity. The link is dofollow wherever you control the markup — your docs, your landing page, your blog. The snippet uses your frozen OSSEAN slug, so it survives a repo rename.