Cursor was huge but it only solved half the problem

We also need a code-aware browser that lets you point and click UI elements and trace that element back to the piece of code that generates it

vibe coding rn is [ide → app]
it should be [ide ←→ app]

✨ Be the training data you want to see in the world ✨ | DΞF | Head of Product Serotonin | building serotonin.co/platform

End state for this of course is [app ↔ app] where you don't need an ide to build applications at all

FID 1580 | Husband + dad (x2). Building @ SkillsEngine. Product, design, code, art, philosophy, systems.

Yeah but still sandboxed within an app that you're building there — I want the full bidrectional browser to ide connection

I believe Replit has this feature now. You can turn on ‘element select’ mode, and click anything on the page and then prompt to edit it.

v0's editor is the closest thing I know of but it's a half measure at best (only usable for front end, locked inside their app vs. general purpose)

The 'click this element' and make a micro change for this component ux is great though

experimenting @rehash // aka @ddwchen everywhere else // treegirl.substack.com // come hang /rehash /tobythecowdog

like a claude interface built into cursor?

currently @openrank prev: buidl.so, threads_reader
https://dharmi.notion.site

There are some browser extensions that make it easier but with all the virtual dom shenanigans that happen in things like react it can be hard to trace ui back to the original component

Ideal state I just point at something on the browser, say "move this 2px up" or "display this to Fahrenheit" or "add thing xyz to this dropdown" and the browser feeds that request back to the ide with the correct component as context

how different is it from inspect element on browsers?