You are staring at a Bolt preview and something is off. The header overlaps the hero image at 768px, the submit button says "Sumbit," and the footer links are the wrong color. Typing all of that back into the Bolt chat as prose is slow and vague. Bolt then guesses at which element you meant and edits the wrong one.
There is a faster path. Capture the preview once, describe each problem next to the exact spot, and hand Bolt a single link it can read as clean text. Here is the order of steps.
Step 1: Open the capture tab next to your Bolt preview
Go to start a new review in a browser tab. Nothing to install, no extension, no signup. Keep your Bolt preview open in another tab or window so you can flip between them. Use Chrome or Edge if you plan to dictate comments; those support the browser's built-in speech recognition. On Firefox you type instead, and everything else works the same.
Step 2: Capture the preview frame
Click Capture screen. The browser asks which window or screen to share. Pick the tab or window showing your Bolt preview. The current frame is drawn to a canvas as a still image. This is a screenshot, not a recording, so you are freezing one moment of the UI. If you want only the broken header, drag a rectangle to crop the still. Cropping is the only image edit, so frame it tight around the problem area.
The outcome: one captured screenshot becomes an item you can comment on.
Step 3: Pin the exact spot and write the fix request
Add a numbered pin on the overlapping header, then type or dictate the comment. Be specific about the element and the change you want. "At 768px the fixed header overlaps the hero heading; add top padding to the hero or reduce the header height" beats "header looks broken." Numbered pins keep several notes on one screenshot from blurring together. If you have guidance that is not tied to any pixel, add a free-floating comment with no screenshot.
Repeat capture and comment for each issue. One screenshot for the header overlap, one for the misspelled button, one for the footer color. For more on framing a shot so the agent edits the right element, see the notes on framing a screenshot so the agent edits the right element.
Step 4: Publish to get the public link
Click Publish. The review is saved and gets a short public URL of the form /r/<slug>. Anyone with that link can read every screenshot, pin, and comment in the browser. If you published without an account, the review is kept for 30 days; sign in later with Google or a magic link to claim it permanently.
Step 5: Grab the markdown URL for Bolt
The same review is available as plain text at /r/<slug>/markdown. That is the format Bolt reads well: headings, pin numbers, and your comments as structured text, no video to transcribe and no screenshot it has to interpret blind. Details on why this format lands cleanly are covered on the Bolt agent workflow page and in the primer on markdown screenshots.
Step 6: Paste the URL into the Bolt chat
Back in Bolt, paste the markdown URL into the chat with a short instruction: "Here is a review of the current preview. Fix each numbered item." Bolt reads the structured list and works through the header overlap, the typo, and the footer color in order. Because each item names an element and a desired change, there is far less guessing about scope.
If a fix comes back wrong, do not retype the problem. Capture the new preview and publish a fresh review, then paste the new URL. Each round is a clean artifact, which keeps the feedback loop for vibecoding tight instead of turning into a long chat thread nobody can follow.
What each output is for
The single review you published serves more than the agent. The markdown feeds Bolt. The public /r/<slug> link is for a teammate or client who wants to read the same notes in the browser and post a comment on any item. You can export the same review as a PDF or Word document for anyone who wants a file. One capture, several receivers.
| Receiver | Format |
|---|---|
| Bolt | markdown at /r/<slug>/markdown |
| Teammate or client | public link at /r/<slug> |
| Anyone who wants a file | PDF or Word export |
After Bolt ships the fix
People with the link can post a comment on any item, and you can mark each one resolved as Bolt closes it out. That gives you a running record of what was reported and what got fixed, without a bug tracker or workflow board. See how to resolve review comments without a bug tracker for the mechanics.
Next time a Bolt preview looks wrong, capture it, pin the spots, publish, and paste the markdown URL. Start your first one at the AI coding agents hub and pick Bolt.