How to let non-technical clients request changes on a live site

If you build software for other people, the loop is familiar. You ship, and the changes come back as emails, marked-up screenshots, and messages like "can you make the headline bigger?" You turn each one into a task, build it, send a link, and wait for the next round.

The slow part is not the feedback. It is the translation. Someone describes a change in their own words, in a separate tool, with no link to the thing on the page. You rebuild the context yourself: which page, which button, what exactly. Every hop loses detail.

What you want is a request that carries its own context: the page, the exact element, and a screenshot, captured the moment the person points at it.

The loop that works

  1. The user points at the live site and describes the change in plain words.
  2. The request lands on your board with the page URL, the element (CSS selector and HTML), and a screenshot.
  3. Your coding agent (Claude Code, Cursor, Cline, Codex, Lovable) reads it, makes the change on a branch, and opens a pull request.
  4. Your host (Netlify, Vercel, wherever you deploy) builds a preview from the pull request.
  5. The requester previews and approves, or asks for a revision. No GitHub account needed.
  6. You merge and ship.

Nothing touches your stack directly. The agent proposes a pull request, and you decide what merges.

Why route it through your agent

Agents make good small changes when they have context. A request with the exact element and page gives them something concrete, and you get a real diff to review. An MCP connector lets your agent pull requests, read the detail, attach a preview, and update status from inside the tool you already code in.

When it fits

Freelancers and agencies shipping client sites. Small teams where a non-technical founder or designer keeps sending changes. Anyone already building with an AI agent who wants feedback to land where they work. It is less useful for large feature work, or when your reviewers are developers who would just open the pull request themselves.

Set it up with Amendor

Add one script tag to the site you ship. The trigger can be a floating button or any element you choose:

<script src="https://amendor.site/widget.js" data-project="YOUR-PROJECT-KEY"></script>

Then connect your agent. Local agents use the amendor-mcp connector (the settings page hands you a ready-made command with your token). Cloud agents connect to https://amendor.site/mcp with a token from settings. Now ask your agent to list the change requests, pick one, and build it.

Questions

Does the requester need a GitHub account? No. They request and approve from a link. Only you touch GitHub.

Does it change my code automatically? No. The agent opens a pull request. Nothing merges without you.

Which agents work? Any MCP client: Claude Code, Cursor, Cline, Codex, and remote agents over HTTP.

Remove the translation step. Let people ask for changes where the change lives, on the live site, and let your agent turn each ask into a pull request you can review. See it at amendor.site.