Getting feedback into Cursor

This page is part of the guides hub on connecting visual product feedback to AI coding agents. It is the Cursor-specific playbook; the cross-agent version lives at how to give feedback to an AI coding agent.

What you'll learn

• The three ways to get feedback into Cursor
• When to use each, with concrete examples
• How Cursor processes embedded screenshots inline
• The @file reference pattern for repeat usage

The three ways to get feedback into Cursor

1. Paste a markdown URL. The simplest path. Open Cursor, hit Cmd-L for the composer, paste the CobaltCapture review URL with a one-line prompt: "Address the items in this review in order: cobaltcapture.com/r/abc12345." The composer follows the URL, pulls the markdown content into the context window, and renders the embedded screenshots inline.

2. Paste raw markdown. Open the review URL in your browser, hit "Copy as markdown," paste the whole thing into the composer. The findings appear inline as headings and image references. The composer processes the embedded URLs the same way it would on a follow.

3. @file reference to a .md in the project. Download the markdown export to your repo root: curl -fsSL https://cobaltcapture.com/r/<slug>/markdown > feedback.md. Then in any Cursor composer chat, type @feedback.md and the file gets included as context. The reference works across sessions; you can come back tomorrow and re-reference the same file.

All three paths produce the same outcome, Cursor reads the markdown and the screenshots are processed inline. The choice is about how you want to structure the workflow.

When to use which

Use the URL paste when the review is one-shot and you do not need to reference it again. Pasting the URL is the fastest path: copy, paste, prompt. The composer stays clean; you can scroll back and see exactly what you asked.

Use raw markdown paste when you want explicit control over what is in the context window. URL follows can be flaky on slow networks or when the composer is short on tokens; raw paste guarantees the content lands.

Use the @file reference when the feedback is a repeated artifact, design reviews you revisit across iterations, staging passes you re-run before each merge. The .md lives in the repo, gets committed with related changes, and becomes part of the project's history. Future Cursor sessions can reference the file by name without paste-and-pray.

A useful pattern: paste the URL for the first iteration, download the .md to your repo if you keep coming back to it, then @file from there forward.

A walkthrough

Open Cursor on the project you are working in. Open your staging build in a browser tab. Open CobaltCapture in a third tab.

Capture the staging build at CobaltCapture. Drag a box around the broken submit button. Dictate: "The submit button overflows the container at viewport widths under 380px on iOS Safari. Should respect the existing max-width 100% on .btn-primary." Repeat for any other findings. Hit Publish.

You get a URL like cobaltcapture.com/r/abc12345. Back in Cursor, hit Cmd-L. Type:

Address the items in this review in order. Confirm each fix before
moving to the next: https://cobaltcapture.com/r/abc12345

Cursor follows the URL, reads the markdown, fetches the embedded screenshots inline as visual context, and starts working through the findings. For each finding it understands the source URL on the page, the screenshot of the problem, and your dictated explanation of the why. It proposes a patch, you confirm, it moves on.

If you want to keep the review as a repo artifact for future Cursor sessions, save it: curl -fsSL https://cobaltcapture.com/r/abc12345/markdown > feedback.md. From now on you can reference it as @feedback.md in any composer chat in this project.

How CobaltCapture fits in

CobaltCapture is built for the moment after the screenshot, producing the markdown URL that Cursor follows or the .md file that lives in your repo. The capture flow takes about a minute for three to five findings, voice dictation handles the "why" without typing, and the published URL is the artifact. See feedback for Cursor for the dedicated workflow page.

Frequently asked questions

What is the fastest way to get visual feedback into Cursor?

Paste a CobaltCapture review URL directly into Cursor's composer. The composer follows the URL, fetches the markdown, and renders the embedded screenshots inline as visual context for the next prompt.

Does Cursor process embedded images in markdown?

Yes. Cursor's composer accepts pasted markdown and processes any embedded image references inline. Stable public URLs work best, the composer needs to fetch the image, not rely on a local file path.

Can I reference a feedback.md file across Cursor sessions?

Yes. Save the markdown export to your repo root as feedback.md. Use Cursor's @ reference syntax to pull the file into any composer chat. The file persists across sessions and survives context compaction.

What is the difference between pasting a URL vs pasting raw markdown?

Pasting a URL is one line and keeps the composer clean, Cursor follows the URL on demand. Pasting raw markdown puts everything in the composer up front, which is useful when you want explicit control over the context window.

Will Cursor follow a URL to fetch the content?

Cursor's composer follows pasted URLs to read their content. Cobalt review URLs return markdown that the composer ingests directly. Embedded image URLs in that markdown get fetched as inline visual context.

Frequently asked questions

What is the fastest way to get visual feedback into Cursor?

Paste a CobaltCapture review URL directly into Cursor's composer. The composer follows the URL, fetches the markdown, and renders the embedded screenshots inline as visual context for the next prompt.

Does Cursor process embedded images in markdown?

Yes. Cursor's composer accepts pasted markdown and processes any embedded image references inline. Stable public URLs work best, the composer needs to fetch the image, not rely on a local file path.

Can I reference a feedback.md file across Cursor sessions?

Yes. Save the markdown export to your repo root as feedback.md. Use Cursor's @ reference syntax to pull the file into any composer chat. The file persists across sessions and survives context compaction.

What is the difference between pasting a URL vs pasting raw markdown?

Pasting a URL is one line and keeps the composer clean, Cursor follows the URL on demand. Pasting raw markdown puts everything in the composer up front, which is useful when you want explicit control over the context window.

Will Cursor follow a URL to fetch the content?

Cursor's composer follows pasted URLs to read their content. Cobalt review URLs return markdown that the composer ingests directly. Embedded image URLs in that markdown get fetched as inline visual context.