Hi Product Hunt — I’m Suyog, building Feedbacks at Softinator TechLabs. A screenshot can show where something is wrong. The handoff still loses the original page, the exact wording someone wants changed, what happened before a bug, and what the developer’s coding agent needs to investigate. We built Feedbacks to keep those pieces together. Point at a website, mark the screenshot and explain the change. For harder bugs, explicitly record a session and inspect its activity, console and network timeline together. Save a frame when one moment explains the problem best. Then give your coding assistant the same thread, images and approved project context through MCP. It can read the evidence and discuss the requested work while you decide what to implement. That shared context is the part we care about most. The complete app, Chrome extension and agent interfaces are Apache-2.0. You control the server and data. The new one-command local setup keeps PostgreSQL and screenshots in Docker volumes, so trying the workflow needs no cloud-storage account. Shared HTTPS deployment has its own guide. Infrastructure and any optional model service remain your costs. Try the walkthrough, or install it and send your first marked screenshot to your coding assistant. Which part of the feedback-to-fix handoff do you still have to reconstruct manually? I’d love to hear where it helps, where setup gets difficult, and what you would change.

Feedbacks

Team and client annotations for developers and AI agents

Team and client annotations for developers and AI agents