Launched this week
Qursor
Point at any UI to send exact context to your AI
545 followers
Point at any UI to send exact context to your AI
545 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.
Qursor
@ely8 Thanks a lot, really appreciate you sharing this. This exact Inspect plus screenshot dance is what made me build Qursor.
Now you can just point at the element and grab selectors plus styles in one go so your agent understands the change without extra explanation.
Apart from that, a single 1440×720 screenshot can quietly eat a few hundred tokens, and if you do that 10–15 times a day it adds up fast, so sending lean selectors and styles instead saves a lot of those credits.
Contral
@theomkarbirje Love this. The fact that it came from a real workflow pain makes it immediately click.
I've lost count of how many times I've had to fight an AI agent just to modify a specific UI element, and the back-and-forth can get ridiculous. Giving agents structured context instead of making them guess from screenshots feels like a very obvious solution in hindsight.
Congrats on the launch. Curious to learn more about the business behind it as well. What's the best email to reach you on? Would love to connect and explore a few ideas.
Qursor
@samagra_gune Thanks so much, that means a lot. This all came straight out of that same “fighting the agent just to change one element” loop, so it is really cool to hear it clicks for you. you can reach me at helloatomkarbirjedotcom.
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?
Qursor
@ianhxu Great question. In practice the copied context is surprisingly small – usually just a few hundred tokens even on a busy page – so it is tiny compared to a screenshot and nowhere near half of an agent’s window. Also, it has 4 modes, so you can go even smaller or increase if you wanted to give clearer context.
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.
Qursor
@luca_capone You are describing exactly the same leak I ran into. With Qursor, it is not just the visual; it grabs the element plus structured context around it: selectors, classes, inline styles, and layout info, so the agent can see both what it looks like and where it lives in the DOM.
In short, the thing you do in ClaudeCode of describing, instead you start Qursor and point to which element you wanted to change, click and annotate here. You can do multiple annotations on this page and then copy all annotations for Claude Code to do.
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.
Qursor
@farrukh_butt1 Client feedback is where this hurts a lot. With Qursor, they can still click on “change this section,” but instead of a blurry screenshot, you get the exact element with selectors and styles you can hand straight to a dev or an 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.
Qursor
@henry_habib Qursor works the same way on internal tools and SaaS dashboards as long as you can open them in Chrome, so you can point at elements in your admin panels or internal UIs just like on public sites.
how it handel the framework code when we inpect those elements ?
Qursor
@saad_nadeem3 Qursor does not care which framework you use because it reads from the rendered DOM, so when you point at something, it grabs the real element with its selectors and styles.
this is cool, can I use this to fix my webflow design?
Qursor
@chintant As much as I know, Webflow is a visual editor where you design directly in the dashboard, not an AI agent. Qursor is most helpful when you are working with AI coding agents or chat-based tools and need to send them precise UI context.