theORQL

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.

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.

Congratulations on the launch! AI with frontend works really well, many people automate exactly this part.

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! one of the biggest pain points is when Cursor or Claude decides to "fix" a CSS

Congratulations on the launch, Shane🎉

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!

AI Made Coding Faster But Debugging Is Still Stuck in the past. After 10+ years as a software engineer, one thing hasn’t changed: Debugging is where most of the real time is lost. The ability to captures runtime errors directly from Chrome:• stack traces with real values• DOM & component state• network failures• user interactionsis impressive, highly recommend this tool !!!

The vision-based verification loop is what makes this stand out. I spend way too much time on the "tweak CSS, refresh, check, repeat" cycle — having something that can actually see the rendered output and confirm the fix landed correctly before I commit sounds like it'd save me hours every week. Curious how it handles responsive layout bugs across breakpoints.

Hey Product Hunt!!!We built theORQL because most AI coding tools are blind: they generate code that looks right in text, but renders wrong in the browser.theORQL closes the loop between your UI and your codebase:takes screenshots of the UI (full page + elements)reads DOM + computed styles + network + consolemaps a UI element to the owning component (via source maps)applies a change, visually verifies it in the browser, then gives you a reviewable diff (no auto-commit)If you try it, what should we focus on next: layout/CSS issues, state bugs, or flaky/hard-to-repro bugs?And what’s one workflow you’d pay to never do manually again?