Patchrooms for Claude Code

Add visual feedback to your Claude Code app

Claude Code is Anthropic’s agentic CLI that edits your codebase and runs your project from the terminal. Patchrooms layers element-anchored feedback on top, so every comment turns into agent-ready context.

Try the live demo

Why Claude Code teams need visual feedback

  • Claude Code works against your real repo, so the higher-quality the feedback, the fewer round trips.
  • A screenshot in a chat does not tell the agent which selector changed or what the goal was.
  • Patchrooms gives Claude Code element-anchored reports with goal and constraints already attached.
  • That means fewer clarifying questions and a fix that lands on the first attempt.

How Patchrooms works with Claude Code

  1. Embed Patchrooms on the app you review

    Add the script to your preview build. Claude Code keeps editing code; Patchrooms gathers feedback on the running result.

  2. Collect agent-ready reports

    Reviewers comment on elements. Each report includes the selector, screenshot, goal, and constraints.

  3. Feed reports to Claude Code

    Paste the Markdown export into your Claude Code session, or connect the Patchrooms MCP server for direct reads (available now).

What your agent receives

Each pinpoint comment exports as clean Markdown with the element selector, the page and viewport, and the console state alongside the ask.

## Feedback: Checkout submit button

Element: button[data-patchroom-id="checkout-submit"]
Page: /checkout · 1440×900 · Chrome 126

Issue
Stays clickable while required fields are empty and
submits an invalid form.

Expected
Disabled until the form is valid: reduced opacity
+ aria-disabled="true".

Console
POST /api/order 422 (validation_failed)

Add it in one prompt

Paste a script tagAdd in one prompt

Ask Claude Code to wire Patchrooms in for you, paste this prompt:

Add the Patchrooms review widget to the project. Insert this script tag into the main HTML template before the closing </body> tag, exactly as written:

…then give it the snippet below. It loads on the live preview and turns on artifact-review mode: pinpoint comments anchored to the elements your reviewers click.

<script src="https://room.patchrooms.com/v1/patchrooms.js"
        data-project-key="pr_xxx"
        data-source="claude-code"
        data-mode="artifact-review"></script>

Or try it locally: no account, no key, no server

Reviewing a Claude Code artifact on your own machine? Run Patchrooms in local mode: no account, no project key, zero network calls. Pinpoint comments stay in your browser and export to Markdown you paste straight back into Claude Code.

<script src="https://room.patchrooms.com/v1/patchrooms.js"></script>
<script>
  Patchrooms.init({ storage: 'local', mode: 'artifact-review' });
</script>

Review workflow

Share the preview link with your team or client. Anyone clicks an element, types a comment or records a voice note (Patchrooms auto-transcribes it to clean text), and captures the selector, a screenshot, and the page context. Every comment carries a status (new, triaged, in-progress, closed) so nothing falls through the cracks. See the full UI review workflow.

Export feedback to your AI agent

Each report exports as clean Markdown with the element selector, a screenshot reference, and the artifact goal and constraints. Paste it straight into Claude Code and the agent fixes the exact issue: this is the heart of AI artifact review. The Patchrooms MCP server lets agents read reports directly (list_reports / get_report) and triage them (set_status). Available now; extended MCP tools (create_room, issue creation) are planned, and a @patchrooms/react package is coming for tighter React integration.

FAQ

Can Claude Code read Patchrooms reports directly?
Direct reads via the Patchrooms MCP server (list_reports / get_report) are available now. You can also paste the Markdown export into your Claude Code session as context. Status writes (set_status) are available now; extended MCP tools are planned.