Product feedback for Vercel previews

CobaltCapture lets a Vercel user review a preview deployment in the browser and walk away with a markdown document a coding agent or a teammate can act on immediately. You open the preview URL, hit Capture screen, crop the still to the part that matters, dictate what is wrong out loud, and publish. The output is a public review at cobaltcapture.com/r/<slug> plus a one-click markdown export, no install, no signup to try, free.

This is a compatibility page, not an integration. CobaltCapture has no API connection to Vercel. It works alongside Vercel for two plain reasons: it reviews any URL in the browser (a preview deployment is just a URL), and its output is markdown that pastes into anything, including the PR that produced the preview.

Where Vercel feedback gets lost

Vercel gives every push a preview URL, which makes it easy to look at a change before it ships. The hard part is what happens after you look. You spot that the hero wraps badly at 1280px, the CTA uses a near-miss shade, and the form spacing doubled since the last deploy, then you have to describe all of that in a PR comment or a chat message. Typed sentences flatten visual problems, screenshots dropped into a comment lose the context of which preview they came from, and the reasoning behind each note never makes it into writing. The reviewer sees everything; the record keeps almost none of it.

Review the preview, publish the markdown

Open your Vercel preview URL in one tab and cobaltcapture.com in another. Hit Capture screen and pick the preview window. Drag a box around the broken hero. Hit Dictate and talk through it: "the eyebrow copy should sit closer to the headline, the headline weight is too heavy, and the CTA gradient is pointing the wrong way." Repeat for the navbar, repeat for the form, then Publish.

You get a review URL where every screenshot is cropped, every finding is captioned, and your spoken reasoning is written out under each frame. The source URL of the preview travels with each item, so anyone reading the review knows exactly which deployment you were looking at.

Paste it where the work happens

The review is built to leave CobaltCapture. Click the markdown export and paste it into the GitHub or GitLab pull request that triggered the Vercel preview, the screenshots and notes render inline in the comment. Or paste the same markdown into a Cursor or Claude Code prompt and let the agent work through each finding against the preview you reviewed. Or drop it into a Linear ticket, a Notion doc, or a Slack message, anywhere markdown is accepted, the document fits.

That is the whole connection to Vercel: review the preview Vercel deployed, then paste the result into the place you already track the change. You keep using Vercel exactly as you do today.

Why this beats a screenshot or a recording

A raw screenshot pasted into a PR loses the preview URL it came from and the reasoning behind the change. A screen recording forces the reader to scrub video and strips the narration the moment an agent tries to read it. A markdown review keeps the cropped frame, the source preview URL, and the dictated "why" together in one pasteable document, which is the format both humans and coding agents read without extra work.

If your reviews routinely run against deployed previews and staging environments, the staging site review and pull request review playbooks cover the same workflow in more depth.

Frequently asked questions

Does CobaltCapture integrate with Vercel?

No, and it does not need to. CobaltCapture is a browser tool that reviews any URL, including a Vercel preview deployment. You open the preview, capture and crop the screens, dictate your notes, and publish a review at cobaltcapture.com/r/<slug>. There is no API connection to Vercel; you just point it at the preview URL like any other page.

How do I get my review back into a Vercel pull request?

Every CobaltCapture review has a one-click markdown export. Copy it and paste it into the GitHub or GitLab PR that triggered the Vercel preview. The cropped screenshots, the source preview URL, and your dictated notes all travel as plain markdown, so they render in the PR comment without an upload step.

Can a coding agent read the feedback I capture on a preview?

Yes. The markdown export is plain text with image links and per-frame captions, which is the format Cursor, Claude Code, and similar agents read directly. Paste the review URL or the exported markdown into the agent prompt and it can work through each finding against the exact preview you reviewed.