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
Hey Product Hunt! I'm the maker of Qursor, and honestly, this started as a personal frustration.
I was using AI agents to make UI changes and kept running into the same wall: the agent would edit the wrong element, or I'd burn 10 prompts just trying to describe "that blue button on the pricing page." Screenshots helped a little, but agents still had to interpret them, wasting tokens and time.
So I built Qursor. It lets you point at any element on any website, and it copies structured, code-aware context, selectors, classes, styles, fonts, and colors directly into your clipboard. Paste it into your agent, and it knows exactly what to change.
What you can do today:
- Visually inspect any UI element (fonts, colors, spacing, layout)
- Copy AI-ready context with selectors, classes, and your own notes
- Extract components as HTML, CSS, or JSX
- Pick exact colors and detect fonts from any site
- Download SVGs, PNGs, JPGs without digging through network tabs
- Let clients annotate exactly which element they want changed
No competitors I know of - I just had the problem, built the solution, and some early users told me it saved them real time.
Free plan available (3 picks/day). Lifetime deal at $39.
Would love your feedback - especially how you're using AI agents for UI work today!
Hey, that's smart, great idea. I use Tidewave, and that includes a pointer as well, but it only works with certain frameworks, so your extension might be what I need for other projects, I'll check it out!
@theomkarbirje This solves a very real context problem. A lot of AI help breaks down because describing the UI manually is slow and incomplete. Pointing at the exact screen state feels much closer to how people naturally ask for help.
Honestly this scratches an itch I didn't know I could fix. Half my back-and-forth with agents is just me describing "no, the button next to that one" and praying it gets it. Sending exact context (classes, styles, fonts) instead of a vague screenshot makes way more sense. Clean execution too. Congrats on the launch 👏
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.
Just use MСP Сhrome Dev Tools for your AI agent and it will be able to see the page, no need for any additional services that transfer the UI into the context
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.
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 'agent edited the wrong element' problem hits way too close to home. I've definitely wasted a bunch of prompts just trying to describe which button I meant. Pointing at the element and grabbing the actual selectors/styles is so much cleaner than throwing a screenshot at it and hoping. Going to give the free plan a spin on a project this week
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?
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.
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.
About Qursor on Product Hunt
“Point at any UI to send exact context to your AI”
Qursor launched on Product Hunt on June 12th, 2026 and earned 238 upvotes and 31 comments, earning #2 Product of the Day. 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
Qursor was featured in Productivity (653.6k followers), Developer Tools (513.9k followers) and Artificial Intelligence (470.8k followers) on Product Hunt. Together, these topics include over 310k products, making this a competitive space to launch in.
Who hunted Qursor?
Qursor was hunted by Omkar Birje. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how Qursor stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Omkar Birje