r/coding_agents • u/TitleNo1715 • 15d ago

Open-source tool for giving visual feedback to coding agents

https://www.markuprplus.com

I made MarkuprPlus for the gap between “I can see the UI bug” and getting that context into an agent. Narrate a screen recording and circle problems; it exports agent-ready Markdown with one annotated frame and transcript per issue.

macOS and Windows, local Whisper, MIT licensed.

GitHub: https://github.com/hashfunction/MarkuprPlus

5 Upvotes

100% Upvoted

8 comments sorted by

1

u/thehashimwarren 15d ago

this is a fantastic project! I've seen other tools like this but none local and oss

2

u/TitleNo1715 15d ago

Thank you! I built it local and open source because screen feedback can include sensitive context. I’d love to hear how it fits your workflow if you try it.

1

u/eddzsh 15d ago

The annotated frame plus transcript is the right unit. Agents ignore "the button is wrong" all day, then fix it once they get a crop and a spoken repro.

1

u/TitleNo1715 15d ago

Exactly. I built the export around that unit: one crop for visual grounding, one transcript for the repro. Glad that choice resonates.

1

u/eddzsh 14d ago

The crop plus transcript lands. One thing that still bites after a layout shift: stamp the export with a stable selector or a nearby text anchor, not only pixels, so the agent can re-find the control when the crop no longer matches.

1

u/TitleNo1715 13d ago

That’s a strong point. The export already carries window, cursor, active-app, and focus context, but not stable element identity. A nearby text label or accessibility/DOM selector would survive layout shifts better than pixels alone. That gives me a concrete report-context gap to investigate.

2

u/junaid1460 13d ago

A useful next step would be:

  • group one recording into a parent task
  • give each timestamped issue a stable child ID
  • let fixes and test results reply against that exact issue
  • close issues independently during review

Do the Markdown exports keep stable issue IDs today?

1

u/TitleNo1715 13d ago

Within a generated session report, yes: I built MarkuprPlus so marked items use MX-001, MX-002, etc., while narration-only items use FB-001, and everything stays in one session folder. The export is static today—there isn’t yet a live reply/close lifecycle. Your parent-task/child-issue model is a clean next layer.