theORQL - Cursor for frontend. Build and debug in Chrome and VS Code.
theORQL is vision-enabled frontend AI. It takes UI screenshots, maps UI → code, triggers real browser interactions, and visually verifies the fix in Chrome before shipping a reviewable diff — so UI fixes land right the first time. 1200+ downloads to date. Download free on VSCode and Cursor.
Replies
Sellou
Congratulations on the launch, Shane🎉
Congratulations! one of the biggest pain points is when Cursor or Claude decides to "fix" a CSS
theORQL
@ben_gend Thanks Ben!!! yes exactly the pain point we're solving. Tons more to come too in the coming weeks please stay tuned!
theORQL
Wow we're so humbled by all the outreach and support! Thank you to all our users, commenters, and special thanks to @fmerian for hunting theORQL!
Clicking a broken element in Chrome and landing on the owning component via source maps... that's the step most debugging workflows make you do manually. theORQL automating that lookup is the difference between guess-and-check and point-and-fix. Shipping a reviewable diff instead of auto-committing is a smart call too. AI tools that auto-apply changes erode trust fast, so review-first builds the habit that gets this used daily instead of tried once. Source map resolution with deeply nested component wrappers will be the real stress test.
Congratulations on the launch! AI with frontend works really well, many people automate exactly this part.
theORQL
3 console errors. theORQL detects them, reads the source files, traces the issue to a missing await on an async call, and proposes a fix. No copy-paste into your AI chat. No switching out of Chrome. This is what debugging without context-switching looks like.
Honest take: I ignored this at first because "Cursor for frontend" sounds like marketing. Then I saw the visual verify loop -screenshot, fix, check in browser, diff. That's not Cursor. That's something Cursor can't do. The bet that AI dev tools need vision, not just bigger models, is one I'd put money on. For next focus - layout/CSS issues. That's where the gap between "code looks right" and "renders wrong" is widest.