Cursor · AI tool

Get client feedback on pages built in Cursor

Built a page in Cursor? Upload the HTML file or paste a deploy preview link, let clients pin comments with no account, then paste one brief with CSS selectors into Cursor's chat to make every change.

Free for 3 projects. Reviewers never need an account. Or upload an HTML file.

Why Cursor users use HTMLAnnotate

Cursor is where you write the code, but your client is not going to open your editor. Once a page looks right on your machine, you still need people who do not code to look at it and say what is wrong. The usual route is a deploy link plus an email asking for thoughts, and what comes back is a set of screenshots, a list of loose bullet points, or a call you have to take notes on.

Cursor's browser and Design Mode let you point at an element yourself and send a note to the agent. That is quick for your own changes, but it only works inside Cursor, on your machine. Your client cannot use it. So their feedback arrives without the element, the page or the screen size attached, and you spend time finding the right component before you can ask the agent for anything.

HTMLAnnotate gives clients a link they can comment on directly. They click the element they mean and type. Each comment records the element, its CSS selector, the page path, the view, and their browser, OS and screen size. When the round is in, Copy for AI copies every open comment as one brief. Paste it into Cursor's agent chat, and the selectors point it at the right markup in your code.

How it works with Cursor

Three steps, about a minute.

Share the page

Upload one self-contained HTML file (up to 1 MB on Free, 10 MB on Pro and Team), or paste a public deploy preview link. Staging behind a browser password box works too: the import page asks for the login.

Collect comments

Send the review link. Clients give a name and email once, switch to Comment mode, and click any element to leave a note. No account, no install.

Paste into Cursor

Press Copy for AI and paste the brief into Cursor's agent chat. Each item has the element, CSS selector, view, page path and any suggested text.

A full review round, start to finish

What a typical round looks like on Cursor.

Choose how to share
For a single static page, ask the agent to put all CSS and scripts inline and upload that one HTML file. For anything with a build step, routing or several files, deploy a preview to your host and use that public URL. A localhost address will not work, because reviewers need a link they can open.
Protect staging if you need to
If your preview sits behind HTTP basic auth, the browser password box, enter the login when the import page asks for it. It is stored encrypted and reviewers never see it. Previews that need a sign-in form, such as Vercel team protection, cannot be imported yet.
Send the review link
Share the HTMLAnnotate link with your client. The page runs live with its own scripts, so interactions behave as they will in production. On a deployed site, reviewers can move between pages and each page keeps its own comments. Forms cannot be submitted on the reviewed copy.
Get specific comments
Reviewers use Browse mode to explore, then Comment mode to click a heading, button, image or SVG and type. Ask them to set a label, such as Bug, Copy or Design, and to check Tablet and Mobile views. Copy edits can go in as suggested text that previews live.
Triage before you prompt
Reply to questions, @mention a teammate, set priority, and resolve anything you will not change. Accept the suggested text you want. The aim is a list of open comments that are all real tasks, because that is exactly what Copy for AI will hand to Cursor.
Hand off to Cursor and sign off
Press Copy for AI, paste the brief into Cursor's agent chat, and review the diff it proposes. Deploy a new preview or upload the updated file, send the link, and ask the client to press Approve. Export the round as CSV if you track work elsewhere.

Cursor's own tools and HTMLAnnotate

Use both. Here is what each is good at.

What you need	Cursor	HTMLAnnotate
Point at an element and request a change	Design Mode in Cursor's browser, for you	Comment mode, for anyone with the link
Feedback from clients who do not code	Not built for this	Yes, no account needed
Hosting a shareable page	No, deploy elsewhere	Upload one HTML file or paste a link
Send feedback to the AI	Design Mode notes go straight to the agent	Copy for AI brief, pasted into Cursor
Device-specific notes	Not covered	Separate Desktop, Tablet and Mobile comments
Sign-off and records	Not covered	Approve button, resolve, CSV export

What works

CSS selectors in the brief map straight to your markup
Clients comment without installing anything or creating an account
Works with single HTML files and public deploy previews
Staging behind a browser password box, with the password kept from reviewers
Phone, tablet and desktop comments kept apart
CSV export of the whole round

Good to know

Uploads must be one self-contained HTML file (up to 1 MB on Free, 10 MB on Pro and Team). Projects with a build step or several files should be shared as a deployed link.
There is no direct MCP connection to Cursor yet. Copy for AI and paste is the way in for now.
Localhost links cannot be reviewed, and previews behind a sign-in form, such as Vercel team protection, cannot be imported yet.

Tips for better Cursor reviews

Ask the agent to inline everything

Before uploading, ask Cursor's agent to produce a single HTML file with CSS in a style tag, scripts inline and images as data URIs or absolute URLs. That keeps the file self-contained and under the upload limit (1 MB on Free, 10 MB on Pro and Team).

Add a project rule for briefs

Cursor reads project rules from .mdc files in .cursor/rules. Add one that tells the agent to treat pasted HTMLAnnotate briefs as a task list, match each CSS selector in your code, and fix one item at a time.

Keep selectors meaningful

The brief is only as useful as the selector it contains. Stable class names or ids on key sections make it easy for the agent to find the right component, compared with long chains of generic div selectors.

Use a password box, not a login

If staging must stay private, protect it with HTTP basic auth so the browser shows a password box. HTMLAnnotate can store that password encrypted. A sign-in form page cannot be imported yet.

Questions about Cursor

What is in the Copy for AI brief?

Each open comment with the element, its CSS selector, the view (Desktop, Tablet or Mobile), the page path, any suggested text change and the replies. Paste it into Cursor's chat and the agent has what it needs to find each element.

Can I use a localhost link?

No. Reviewers need an address they can open from their own browser. Upload a single HTML file, or deploy a preview to your host and paste that public link.

Is there an MCP server for Cursor?

Not yet. A direct MCP connection is coming soon. For now, Copy for AI works with Cursor, ChatGPT, Claude or any other tool you paste into.

Do clients need Cursor or an account?

No. They open the review link, enter a name and email once, and comment in their browser. Nothing is installed on their machine or on your site.

My project has several files. Can I upload it?

Uploads are limited to one self-contained HTML file. Ask Cursor's agent to inline the CSS and scripts into a single file, or deploy the project and paste the public link instead.

Can I review a password-protected staging site?

Yes, if it uses a browser password box (HTTP basic auth). Enter the login when the import page asks for it. It is stored encrypted and reviewers never see it. Sign-in form pages cannot be imported yet.

Other AI tools

HTMLAnnotate works with any page anyone can open in a browser.

Claude ChatGPT Gemini v0 Lovable Bolt Replit +See all