Heckle

Stop being a human screen reader for your coding agent.

3 followers

Stop being a human screen reader for your coding agent.

3 followers

Heckle sits between your browser and your coding agent during development. When something breaks, describe it while you are still in the flow. Heckle captures the screen, user path, DOM, console and network evidence, drafts an agent-ready task, and waits for your approval. Instead of reconstructing bugs from screenshots and DevTools, send the agent the evidence from the moment it happened.

Free

Launch tags:Open Source•Developer Tools•Artificial Intelligence

Launch Team

Viktor.comAn AI coworker that actually does the work

Promoted

Maker

📌

Hey Product Hunt, Sriram here. I built Heckle because I got tired of the bit after the coding agent writes the app. Something breaks, and I am back to screenshots, console errors, network logs, retracing the flow, then writing a paragraph explaining it all to the agent. Heckle runs alongside your app while you test. You say or type what went wrong, it grabs the browser context around that moment, turns it into a task, and lets you approve it before sending it to your coding agent. The thing I’m trying to find out: is this browser-to-agent handoff also a painful part of your workflow, or have you found a better way to deal with it?

Report

2mo ago

Pros

Cons

Reviews