---
title: "Review implementations, previews & UI feedback"
description: "Inspect what an agent built, preview it live, leave UI feedback the agent acts on, and merge the pull request."
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.trevize.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Review implementations, previews & UI feedback

Whether it came from a [task](/concepts/tasks), a
[session](/concepts/sessions), or an [automation](/concepts/automations), every
piece of agent work lands as a reviewable change. This guide covers reviewing it.

1. **Open the implementation**

   Open the implementation to see its **status** and progress. While it runs, it
   shows the **blueprint steps** — *Sandbox setup → Plan → Analyze → Implement → Fix
   issues → Test → Open PR* — and an **iteration** count, so you can see exactly
   where it is.

2. **Preview the change**

   Open the **live preview** to see the change running. If your app exposes more
   than one process, switch between them; use the address bar to navigate.

3. **Leave UI feedback**

   On the preview, choose **Add** to leave a **UI feedback** comment pinned to what
   you see. Each comment is tracked through **open → in progress → resolved** (or
   **ignored**), supports threaded replies, and the agent can act on it — so review
   is visual, not just diff-reading.

4. **Review the diff and pull request**

   Check the **diff** of changed files and the **pull request** on GitHub. From the
   implementation you can **Open PR** (if there isn't one yet), **Merge**, close, or
   re-open it; the PR's status is shown throughout. If a merge is blocked by
   conflicts, ask the agent to **fix conflicts**.

5. **Follow up**

   When the run reaches a terminal state, send **follow-up instructions** to request
   changes or fixes. If a step is waiting on you, **approve** it or reply with
   feedback. With [CI auto-fix](/concepts/workspaces) enabled, a failing CI run can
   trigger an automatic follow-up that pushes a fix.

> **You always merge**
>
> Trevize opens pull requests; it doesn't merge to your default branch on its own.
> Review, request changes, and merge on your terms — just like any contributor.

Source: https://docs.trevize.dev/guides/reviewing-implementations/index.mdx