# Alchemist Work Review

What the Work Review surface collects, how to inspect a completed ticket's diff and reports, and your options when the result isn't what you wanted.

---

Work Review is your project's checklist for confirming that finished agent work is actually what you wanted, before you move on and forget to look. This guide covers what it shows and what to do when a result isn't right.

## What Work Review collects

Work Review lists one row per **conversation thread** the assistant worked on, not per ticket: if a single request in Slack, email, or the dashboard fanned out into several coordinated tickets (see [Alchemist Ticket Dependencies](/docs/guides/alchemist-ticket-dependencies)), that whole scope is still one row here. Each row shows:

- The thread's title and where it came from (dashboard, Slack, or email).
- Its state (discussing, building, queued, done, partially done, or failed) and, for a multi-ticket thread, how many of its tickets succeeded out of the total.
- When it was created, and whether it's still awaiting your review.

Threads awaiting review are pulled to the top of the list and filterable by time window (last 24 hours, 7 days, 30 days, or all time).

## Inspecting a completed ticket's changes

Each row links out to the underlying work:

- **Verify** opens the ticket detail page for the thread's ticket (or its primary ticket, for a multi-ticket scope). That's where the actual evidence lives: the agent graph with each node's status, the per-node reports, the session audit of every agent turn, and the running cost against budget. See [Alchemist Tickets](/docs/guides/alchemist-tickets#reading-the-graph) for how to read that page, and [Alchemist Reports and Audit](/docs/guides/alchemist-reports-and-audit) for how to read the reports and audit trail themselves in depth.
- **Thread** (when different from Verify) opens the original conversation the request came from, so you can see the request in its original context.

Whatever landed is a normal git commit on your project's base branch: from the ticket detail page you can see exactly what changed, and it's inspectable and revertable like any commit in your repository.

Once you've looked things over, check the row off as reviewed. Checking it off is just your own bookkeeping, a way to mark "I looked at this and it's fine": it doesn't change anything about the ticket or the underlying work, and you can uncheck it if you change your mind.

## When the result isn't what you wanted

You have a few options from the ticket detail page, depending on how far off the result is:

- **Retry the ticket.** This resumes from the last good checkpoint rather than starting over, useful when the work is mostly right but hit a snag. See "Retry semantics" in [Alchemist Tickets](/docs/guides/alchemist-tickets).
- **Start fresh.** Discards any committed work on that ticket and re-plans it from scratch. Use this when the underlying approach was wrong, not just an individual step.
- **File a follow-up ticket.** For a result that's functionally fine but needs a different follow-on change, a new, clearly scoped ticket is often faster and clearer than trying to steer the original one further after the fact.
- **Revert the commit.** Since landed work is a normal commit, reverting it (yourself, or via a ticket asking for the revert) is always on the table.

> **Note:** Work Review doesn't gate anything: it's a way to stay on top of what's shipped, not an approval step blocking a ticket's execution. Approvals for budget and awaiting-input decisions happen on the Approvals panel and the ticket detail page itself; see [Alchemist Budgets and Costs](/docs/guides/alchemist-budgets-and-costs) and [Answering Agent Questions](/docs/guides/alchemist-awaiting-input).

## Next steps

From here: [Alchemist Reports and Audit](/docs/guides/alchemist-reports-and-audit) for reading the evidence in depth, or back to [Alchemist Tickets](/docs/guides/alchemist-tickets) for the full ticket lifecycle.