We’re building the bug report you don’t dread.
One capture grabs a bug's full context, the UI, the console, the network request and response, the exact repro, and hands it to your AI agent over MCP, or files it as a clean issue. No screenshots-and-guessing, no days of back-and-forth.
Why we’re building ShotMark.
We’re a developer and a QA. On every project we shipped, the same loop wore us down: a teammate or a user hits a bug, sends a blurry screenshot and a vague “it’s broken,” and then come the days of back-and-forth, what browser, what did you click, what did the console say, can you reproduce it, before anyone can even start on a fix.
“Half the work on any bug was reconstructing what the report left out. We wanted to capture it once and never chase it again.”
The context was always there at the moment the bug happened , the console error, the failing request and its response body, the steps that led to it. It just never made it into the report. So we’re building the tool we always wanted: one click captures the whole picture, and hands it straight to your AI coding agent over MCP, or files it as a GitHub, Linear, or Jira issue.
ShotMark doesn’t auto-fix anything. The agent proposes the change with the full context in hand, and you review it like any other pull request. We’re building it in public, come watch it take shape.
What you can count on.
Your bug data stays yours
Auto-redaction on capture, with self-hosting on the roadmap.
The tools stay free
All 68 developer and QA tools, no signup, no gate, no catch.
We build in the open
A public changelog and blog, honest about what works and what doesn’t yet.
A real human answers
A developer and a QA read every message, never a bot.
Where we are today
68
Free tools, no gate
143
Articles published
15
Topics covered
Weekly
Shipping in public
The people behind it.
Rumana Parvin
Founder & QA Engineer
Breaks it on purpose
The QA half of ShotMark: and the reason it exists. Tired of bug reports that were all screenshot and no substance, she's building the tool that captures the full story the first time.
Want to build this with us?
We’re a small team with room to grow. If shipping a tool developers and QAs actually want sounds like your kind of work, we’d love to hear from you.
Got a question?
Feature ideas, partnership questions, or just curious where we’re headed, send it over. A developer and a QA read every message.