# Website Feedback Tool: Comments on a Live Build That Your Coding Agent Can Read

Canonical: https://commareports.com/website-feedback
Published: 2026-09-30

> Upload a built site, get a hosted preview, and let reviewers select any text on any page to leave a comment. Each comment keeps its page, element and build, and Claude Code or Cursor can pull the list over MCP and resolve items as it fixes them.

# Website feedback your coding agent can act on

An AI tool can now produce a working site in an afternoon. Reviewing it
still takes a week, because feedback arrives as a screenshot with a red
circle, a Slack message that says _"the pricing bit feels off"_, and a
comment about a version you replaced two builds ago. None of it tells
the person — or the agent — doing the fixing _where_.

Comma's **Websites** feature fixes the pointing. Upload the build, send
the preview, and every comment lands on the exact text it is about, on
the exact page, against the exact deployment.

## How it works

1. **Build the site** the way you already do — `npm run build`, `hugo`,
   `astro build`, whatever produces a folder of HTML, CSS and JS.
2. **Upload it** on the Websites tab. A zip with `index.html` at the root
   works, and so does a project zip that contains a `dist/`, `build/` or
   `out/` folder — Comma finds the output.
3. **Comma hosts it** on its own isolated deployment. Your site's code
   never runs on Comma's origin, so it can't reach reviewers' sessions.
4. **Invite reviewers.** They click through the real site, select a
   heading, a button label or a paragraph, and leave a comment. The
   highlight stays on the text for the next reader.
5. **Hand the list to your agent** — or work through it yourself.

## What a comment carries

The reviewer sees a clean thread: their note, the quoted text, replies,
resolved or open. Underneath, each comment also keeps what someone
fixing it needs:

| The reviewer sees         | Also stored with the comment               |
| ------------------------- | ------------------------------------------ |
| Their comment and replies | The page path it was left on               |
| The highlighted text      | A selector for the element                 |
| Open / resolved           | The deployment (the exact build) it was on |

That is the difference between _"the button is wrong"_ and _"on
`/pricing`, the `Buy now` button inside the second card, on build 7"_.

## Close the loop with Claude Code or Cursor

The comment list is available over Comma's [MCP server](/mcp) and the
[REST API](/docs/api):

- `list_websites` and `read_website` find the site and its live build.
- `list_website_comments` returns every comment with its page, element
  and deployment context.
- `set_website_comment_status` marks a comment resolved.

So the loop becomes: reviewers comment, you ask your agent to _"work
through the open comments on the pricing site"_, it edits the code and
resolves each item as it goes, you upload the new build. Reviewers see
their threads resolved instead of being asked whether it's done. Setup
takes a minute in [Claude Code](/mcp/claude-code) or
[Cursor](/mcp/cursor).

## Where it fits against feedback widgets

Tools like Marker.io, BugHerd and Pastel are good at what they are built
for: a widget on a site you already host, feeding screenshots into Jira
or Trello for a person to triage. If that is your process, keep it.

Comma is built for a different shape of work:

- **You don't have a host yet.** The build is on your laptop or came out
  of v0, Lovable or Bolt. Comma hosts the preview for you — no Vercel
  project, no staging environment, no DNS.
- **An agent does the fixing.** Comments come with the context a coding
  agent needs and can be resolved by the agent, not re-typed into a
  ticket first.
- **The site sits next to your reports.** The same workspace holds your
  HTML reports, test results and AI-generated pages, with the same
  comment model.

## Honest limits

- **Reviewers sign in.** A Website is private by default; invite
  commenters or make it public with comments on. For a no-account review
  of a single screen, share it as a [Comma report](/comment-on-html)
  instead — report readers can comment without signing up.
- **Uploads carry text files.** Images and fonts should use absolute URLs
  for now.
- **Unbuilt source needs Vercel.** Built output always works; to deploy
  raw Next.js or Vite source, connect a Vercel account and it builds
  there.
- **Previews expire.** Deployments are review builds, not production
  hosting. Upload again when you want a fresh one.
- **Linked sites aren't annotated.** You can attach an existing URL and
  keep page-level comments beside it, but in-page highlights need a build
  Comma serves.

## Try it

**[Upload a build to Comma →](https://commareports.com/websites)**

### Related

- [Share a v0 design for feedback](/agents/share-v0-output)
- [Share what Lovable built](/agents/share-lovable-output)
- [Share a Bolt project for review](/agents/share-bolt-output)
- [Let an agent respond to comments](/agents/let-an-agent-respond-to-comments)
- [Comment on HTML](/comment-on-html)
- [Vercel alternatives](/alternatives/vercel-alternatives)