Product feedback for GitHub users

CobaltCapture gives a GitHub user a fast way to turn what they see in the browser into markdown that pastes straight into a pull request comment or issue. You open the preview or staging URL, click Capture screen, crop the still, talk through the problem out loud, and hit Publish. The output is a public review link plus a one-click markdown export, with cropped screenshots, source URLs, and your spoken notes as captions, ready to drop into any GitHub thread that renders markdown. There is no GitHub integration, no app to install, and no signup to try.

Where CobaltCapture fits a GitHub workflow

Review happens on a running build, but the conversation happens in the repo. The gap is getting what you saw on screen into a comment without losing the detail. The usual path, screenshot, drag into the comment box, type a sentence, repeats per finding and quickly loses track of which image goes with which note.

CobaltCapture closes that gap with two things that are already true of GitHub: it renders markdown, and it renders markdown images. You review any URL in the browser, a deploy preview linked from a PR, a GitHub Pages site, a staging build, then publish a single markdown document and paste it into the pull request comment or issue. The screenshots render inline, each caption sits next to its image, and the source URL is right there.

How to use it with a pull request

Open the build you want to review. Open cobaltcapture.com in a new tab and click Capture screen, then pick the window. Drag a box around the component that's off, hit Dictate, and describe the issue: "The submit button overflows its container below 380px on iOS Safari." Repeat for each finding, then Publish.

You get a link like cobaltcapture.com/r/<slug> and a Copy as markdown button. Paste that markdown into a PR comment or issue:

## Review of the checkout preview

Three findings against the deploy preview, screenshots and notes below.
(pasted CobaltCapture markdown)

GitHub renders the images inline and the captions stay anchored to them. The same markdown is equally readable by a coding agent that picks up the PR, so the handoff from "here's what's wrong" to "here's the fix" doesn't lose context.

Why markdown is the right format here

A PR comment is markdown, an issue body is markdown, and both render hosted images. That makes CobaltCapture's output portable: the document that a reviewer wrote in the browser is the same document a teammate reads in the thread and a coding agent reads later. Dictation also captures the nuance a typed note skips, "only after scrolling past the fold, only on iOS", which is exactly the context that shapes a good fix.

CobaltCapture doesn't replace anything in your GitHub workflow. You keep reviewing, merging, and tracking work exactly as you do now. It just gives the visual half of the feedback a clean, paste-ready form. For the underlying pattern, see screen capture to markdown, and for applying it to review threads specifically, pull request review.

Frequently asked questions

Does CobaltCapture integrate with GitHub?

No. There is no GitHub API integration, app, or login. CobaltCapture is compatible with GitHub the same way any markdown is: you capture a screen in the browser, publish, and paste the markdown into a pull request comment or issue, where GitHub renders the images and text. Nothing connects to your repo or account.

Will the screenshots show up in my pull request comment?

Yes. Each cropped screenshot is hosted at a public image URL, and GitHub renders standard markdown image syntax inline in PR comments and issues. When you paste the exported markdown, the images appear in the thread alongside your captions and source URLs.

Can I review a deploy preview before it is merged?

Yes. CobaltCapture reviews any URL open in your browser, including a deployed preview, a GitHub Pages site, or a staging build linked from a PR. Capture the screens, dictate what's wrong, publish, and paste the markdown back into the PR so the next person, or a coding agent, has the full context.