Pinpoint - Point at your app; your coding agent gets it

Hi Product Hunt 👋 I built Pinpoint because most of my time with coding agents went into describing *which* thing I meant. "The button under the hero — no, the other one." Screenshots helped a little, but the agent still had to guess which element in the code the pixels came from. With Pinpoint you press ⌥⇧A on your local dev site, click the element and type what should change. Your agent (Claude Code, Cursor, Codex, anything that speaks MCP) gets your words plus the selector, DOM path, computed styles, the React/Vue component, a source-file hint and a crop. If the request is ambiguous it asks back, and you answer right on the page. When it's done you see its reply, a before/after crop, and Accept or Not quite. New this week in 0.7.2, straight from launch feedback: when the element is a reused component, Pinpoint tells the agent how many times it appears and asks whether you mean just this one or all of them — and on minified production builds it finds the original file and component name through the page's source maps. It also works on the iOS Simulator and Android emulator, and can record the steps of a bug. Everything runs on your machine: a small bridge on 127.0.0.1 plus a browser extension. No account, no analytics. MIT licensed. I'd love to hear where it gets in your way, which framework you want it to understand better, and what a note should carry that it doesn't yet.