Bug reports a developer can actually reproduce

CobaltCapture is a free, browser-based way to file a bug report a developer can reproduce without a follow-up conversation. Capture the broken screen, pin the spot, dictate the steps to repeat it and what you expected instead, and publish. The report is one review URL, exportable as markdown that drops straight into your issue tracker or a coding agent.

A bug report fails when the developer cannot reproduce it. That usually means a screenshot landed in one place, the steps in another, and the "what should happen" was never written down. The developer spends twenty minutes reconstructing the context you already had, or bounces it back as "cannot reproduce." The fix is to keep everything in one artifact.

Capture the bug in one pass

Click Capture screen and grab the failing state. Crop to the broken element and drop a numbered pin on it. Dictate the repro steps out loud: "Pin 1, the total shows zero. Steps: add two items, apply the promo code, refresh. Expected the subtotal to persist." Each step lands as editable text next to the screen. If the bug spans several screens, capture each in order, all in the same review.

That produces a QA bug report with the visual, the steps, and the expectation in a single document the developer opens once and acts on.

Severity and priority, stated plainly

A good report says how bad it is and how soon it matters. Those are two different axes, and conflating them is how a cosmetic bug jumps the queue ahead of a checkout blocker. The severity vs priority distinction belongs in the report itself: dictate the severity ("blocks checkout, no workaround") so triage is not guessing. The developer and the PM read the same framing.

What the developer receives

A public review URL, plus a one-click markdown export that pastes into a GitHub or GitLab issue, a Linear or Jira ticket, or a coding agent session. The source URL is stamped on each frame, the pins are burned into the export, and your dictated steps are right there as captions. Nothing is locked in a proprietary viewer the developer has to open and learn.

No install and no browser extension, which matters when QA runs across a fleet of machines and managed browsers where you cannot add extensions. CobaltCapture runs in the browser tab you already have open.

Skip the copy-paste entirely

Two ways to get the report off the review page without hand-copying markdown into a ticket, both real, both free:

Push straight to GitHub. Connect the CobaltCapture GitHub App once and every review you own gets a Send to GitHub button. One click opens a needs-triage issue in the repo you choose, with the screenshots and annotations rendered inline, exactly as they appear on the review. It only reads repo names and writes issues, it can't touch code.

Or let the agent pull it itself. If a coding agent is the one fixing the bug, connect the Cobalt MCP server and skip the export step altogether. The agent calls get_review on the review URL and gets your notes as text plus each annotated screenshot as a real image, the pixels you marked up, not a link it has to fetch and hope resolves.

Get started

cobaltcapture.com, free, no signup to start on your first bug report.

Frequently asked questions

What makes a bug report reproducible?

The developer needs the visual state, the exact steps to reach it, and what should have happened instead. CobaltCapture keeps the screenshot, your dictated repro steps, and the source URL together in one review, so the report is self-contained and the developer is not pinging you for context.

Can I capture several screens in one bug report?

Yes. Each capture becomes its own item with its own pins and note, so a multi-step repro is a sequence of screens in order, each annotated, in one review URL.

Does the export work with our issue tracker and coding agents?

The markdown export pastes cleanly into a GitHub, GitLab, Linear, or Jira issue, and into a coding agent like Cursor or Claude Code. The cropped screenshots, pins, source URL, and notes all come along.

Can I file the bug straight into GitHub instead of copying markdown by hand?

Yes. Connect the CobaltCapture GitHub App once, from any review you own, and a Send to GitHub button appears that opens a needs-triage issue in the repo you pick, with the screenshots and annotations rendered inline. No copy, no paste, no separate ticket to keep in sync.

Can a coding agent read the bug report itself, without me pasting anything?

Yes, over MCP. Connect the Cobalt MCP server to Claude Code, Cursor, or another MCP-aware agent, and it can call get_review on the URL and receive your notes as text plus each annotated screenshot as an actual image, the same pixels you marked up, not a link it has to fetch and hope renders.