Click any UI bug on localhost and your AI agent fixes it
Stop describing UI bugs to your AI. Click any element on your localhost site, say what's wrong, and Claude Code, Codex, Gemini or OpenCode edits the right file. Watch it work live, then approve the diff on the page. Nothing is written until you do.
“The button below the second pricing card. No, the other one.”
When you’re building a website with a coding agent, you can see what needs changing: a button that doesn’t line up, a heading that wraps awkwardly, or spacing that feels off. But getting that change made means turning what you see into a text prompt.
You explain where the element is. Open DevTools. Copy a selector or take a screenshot. Find the component. Switch to the terminal, paste everything in, and hope you’ve given the agent enough context. Then go back to the browser to check the result.
For a small visual change, explaining the task can feel like more work than the change itself. And when there are several things to fix, you repeat that process for each one.
I was already looking at the bug. I just wanted to click it.
That’s why I built PulseDev: to give your coding agent the context behind the element you’re pointing at, alongside your instructions.
From “which button?” to “make this button taller” Click the element on your local site and describe what you want changed. PulseDev attaches the selected element’s context, including its selector and styles. The Vite plugin adds source mapping where supported, helping the agent locate the relevant code.
You still decide what the change should be. PulseDev handles the handoff from the page to your agent.
How it works
Open your local site in your browser and click an element. Shift-click to select more than one.
Describe the change: “Match this button’s height to the one beside it.”
Send it to Claude Code, Codex, Gemini CLI or OpenCode and follow the agent’s activity beside the page.
Review the proposed diff in your browser. Approve or reject it in review mode, or enable auto-apply when you want it.
Built for the tools you already use PulseDev works with your own browser, local project and installed coding agent. Add the widget with a script tag, or use the Vite plugin for source mapping where supported. Your agent’s usual usage limits and provider charges still apply.
It’s for the UI work that adds up: adjusting spacing, matching styles between elements, changing copy, and polishing the details before you ship.
Free for one project on macOS. Pro unlocks unlimited projects. Subscribe before November 3, 2026 for $12/month and keep that rate. New subscriptions are $18/month from November 3. No promo code needed.
I’d love to hear about your workflow - Think about the last UI change you asked a coding agent to make. What was harder: explaining which element you meant, or getting the change right? - How do you share UI context today—screenshots, selectors, file paths, or descriptions? - What would you need to see before trusting the proposed change? - After trying PulseDev, where did you still have to explain yourself?
About PulseDev on Product Hunt
“Click any UI bug on localhost and your AI agent fixes it”
PulseDev launched on Product Hunt on October 27th, 2026 and earned 108 upvotes and 14 comments, placing #10 on the daily leaderboard. Stop describing UI bugs to your AI. Click any element on your localhost site, say what's wrong, and Claude Code, Codex, Gemini or OpenCode edits the right file. Watch it work live, then approve the diff on the page. Nothing is written until you do.
On the analytics side, PulseDev competes within Mac, Developer Tools and Artificial Intelligence — topics that collectively have 1.1M followers on Product Hunt. The dashboard above tracks how PulseDev performed against the three products that launched closest to it on the same day.
Who hunted PulseDev?
PulseDev was hunted by Perlat Kociaj. 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.
For a complete overview of PulseDev including community comment highlights and product details, visit the product overview.
Perlat Kociaj
Hey Product Hunt 👋
“The button below the second pricing card. No, the other one.”
When you’re building a website with a coding agent, you can see what needs changing: a button that doesn’t line up, a heading that wraps awkwardly, or spacing that feels off. But getting that change made means turning what you see into a text prompt.
You explain where the element is. Open DevTools. Copy a selector or take a screenshot. Find the component. Switch to the terminal, paste everything in, and hope you’ve given the agent enough context. Then go back to the browser to check the result.
For a small visual change, explaining the task can feel like more work than the change itself. And when there are several things to fix, you repeat that process for each one.
I was already looking at the bug. I just wanted to click it.
That’s why I built PulseDev: to give your coding agent the context behind the element you’re pointing at, alongside your instructions.
From “which button?” to “make this button taller”
Click the element on your local site and describe what you want changed. PulseDev attaches the selected element’s context, including its selector and styles. The Vite plugin adds source mapping where supported, helping the agent locate the relevant code.
You still decide what the change should be. PulseDev handles the handoff from the page to your agent.
How it works
Open your local site in your browser and click an element. Shift-click to select more than one.
Describe the change: “Match this button’s height to the one beside it.”
Send it to Claude Code, Codex, Gemini CLI or OpenCode and follow the agent’s activity beside the page.
Review the proposed diff in your browser. Approve or reject it in review mode, or enable auto-apply when you want it.
Built for the tools you already use
PulseDev works with your own browser, local project and installed coding agent. Add the widget with a script tag, or use the Vite plugin for source mapping where supported. Your agent’s usual usage limits and provider charges still apply.
It’s for the UI work that adds up: adjusting spacing, matching styles between elements, changing copy, and polishing the details before you ship.
Free for one project on macOS. Pro unlocks unlimited projects. Subscribe before November 3, 2026 for $12/month and keep that rate. New subscriptions are $18/month from November 3. No promo code needed.
I’d love to hear about your workflow
- Think about the last UI change you asked a coding agent to make. What was harder: explaining which element you meant, or getting the change right?
- How do you share UI context today—screenshots, selectors, file paths, or descriptions?
- What would you need to see before trusting the proposed change?
- After trying PulseDev, where did you still have to explain yourself?