Deployment Reviews

Deployment reviews

Deployment reviews let LatchLoop inspect a successful preview deployment in a real browser and report whether the deployed app appears to match the task.

LatchLoop can open the preview, interact with the UI, capture evidence, and summarize whether the task-specific goal looks complete.

---

When deployment reviews run

Deployment review is triggered after LatchLoop receives a successful deployment event for a task.

If a newer deployment review supersedes an older one, the older run is marked as superseded so the task focuses on the latest evidence.

---

Project settings

For each project, you can configure:

• review instructions
• a review start path
• optional HTTP headers for protected previews

Use these settings for project-wide expectations, such as “verify the dashboard loads without console errors” or “start all reviews at /app.”

---

Blocked reviews

Sometimes a browser review would be misleading. For example, the task may require a database migration, edge function deploy, seed data, or a backend rollout before the UI can be tested correctly.

In those cases, LatchLoop can mark the review as blocked before browser launch and show the reason in the task UI.

You can manually rerun the deployment review later after the prerequisite is complete.

---

Reading review results

Deployment review results can include:

• status: passed, failed, blocked, timed out, superseded, or errored
• a video of LatchLoop’s testing
• a summary of what LatchLoop found
• screenshots when available
• notes about missing prerequisites or failed assertions

If a review fails, LatchLoop can use the review findings to focus a follow-up builder run on the exact deployed behavior that needs repair.

---

Troubleshooting

No review appeared after deployment

• Ensure your deployment URL gets automatically added to the PR in Github so LatchLoop can see a deployment exists.
• Confirm the deployment URL is reachable.

The review is blocked

• Read the blocked reason in the task UI.
• Complete the prerequisite, then manually rerun the review if appropriate.

The review failed but the app looks correct

• Check the task objective that was reviewed.
• Update the task or project review instructions if the review was checking the wrong thing.
• Rerun the review after making the expectation clearer.