Launching today
Qursor
Point at any UI to send exact context to your AI
255 followers
Point at any UI to send exact context to your AI
255 followers
I kept wasting AI tokens describing UI changes to agents that edited the wrong element. So I built Qursor. Point at any element, copy structured context (selectors, classes, styles, fonts, colors), paste into your AI agent. No vague screenshots. No burned credits. - Inspect fonts, colors, spacing - Copy AI-ready element context - Extract components as HTML/CSS/JSX - Color picker and font detector - Download assets from any page
Free Options
Launch Team / Built With
Qursor
@theomkarbirje Great idea, thanks for building this. I definitely want to try it.
The biggest pain for me right now is that I usually have to do this through Inspect, and it takes too much time. Styles are not included, so I often end up combining a screenshot with copied source code just to explain one UI change to an agent.
This is exactly the kind of friction that should disappear.
This is a real agent failure mode. More context is useful, but exact target context is what stops the agent from confidently editing the wrong thing.
Curious if you see Qursor staying as copy-to-agent context, or moving toward a guardrail where the agent can propose the patch and leave a receipt of exactly what changed.
Really like this, "agent edited the wrong element" is such a real token-waster. Copying structured selectors/styles instead of a vague screenshot is the right idea. Does the copied context stay small enough that it doesn't eat half the agent's context window on a busy page?
The context problem is the thing nobody warns you about. I vibe-code in Claude Code and Cursor all day with zero coding background, and half my time goes to explaining which button is broken instead of fixing it. Pointing at the actual UI beats pasting a screenshot and typing "the third card on the left," that part kills my flow. Does it send the code behind what I point at, or just the visual? That's where context leaks for me.
The token-waste problem is real. How does Qursor handle stateful elements - like a dropdown that's only visible when open, or a hover state? Those are usually impossible to inspect without freezing the UI somehow.
This would be really useful in client feedback loops too. Instead of someone saying “change this section” and sending a blurry screenshot, they could point to the exact element and pass clean context to the developer or agent.
Voquill
Congrats on the launch!
This looks useful. One thing I'd want to know is whether it works just as well on internal tools and SaaS dashboards as it does on public websites.