Add visual feedback to your OpenCode app

Why OpenCode teams need visual feedback

• OpenCode runs in your terminal against your repo, so it benefits from precise, structured input.
• A vague bug report forces the agent to explore instead of fix.
• Patchrooms supplies the selector, screenshot, and goal up front.
• OpenCode then makes a targeted edit rather than a broad guess.

How Patchrooms works with OpenCode

1. Embed Patchrooms on your preview

   Add the script to the build your team reviews.

2. Capture structured reports

   Reviewers comment on elements; Patchrooms records the context.

3. Pass the report to OpenCode

   Export Markdown and include it in your OpenCode session.

Add it in one prompt

Paste a script tagAdd in one prompt

Ask OpenCode to wire Patchrooms in for you — paste this prompt:

Add the Patchrooms review widget. Insert this script tag into the HTML entry point 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://cdn.patchrooms.com/v1/patchrooms.js"
        data-project-key="pr_xxx"
        data-source="opencode"
        data-mode="artifact-review"></script>

Review workflow

Share the preview link with your team or client. Anyone clicks an element, leaves a comment, and Patchrooms 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 OpenCode and the agent fixes the exact issue — this is the heart of AI artifact review. A Patchrooms MCP server that lets agents read reports directly is planned, and a @patchrooms/react package is coming for tighter React integration.