Skip to main content

Work with tasks

Read review history

Compare current and prior work runs, their review output, comments, attribution, and completion history.

Review history preserves the record of each work run so that a task can be revisited without losing its earlier decisions. Done tasks use an intentionally related green header and Completed review history heading. Closed tasks also keep their work runs and review evidence in a read-only history rather than an active review workspace.

Inspect a work run

  1. Open Review for a Reviewing task, or View review history for a Done or Closed task with saved work runs.
  2. Select a work run from the history.
  3. Use the run-type label to distinguish Person work from Coding-agent work, then read the exact lifecycle times, review outcome, Latest changes, optional code-review link, and ordered review comments.

Coding-agent runs retain the agent-name and resolved-command snapshots that applied when the run was queued. They also show queue attribution, execution origin, any current local-approval wait, elapsed agent-working time, AI hand-off, and recovery facts when those facts exist. A later coding-agent catalog change does not rewrite those snapshots.

Person runs instead show the recorded performer, who started and completed the work, submission and review-resolution times, and direct-completion facts. They do not show a coding-agent command, AI hand-off, listener approval, Start fresh, or recovery disposition.

Earlier runs are read-only. Their comments and output stay attached to the run that produced them, even after a follow-up or fresh run changes the task's current state.

When the task is excluded from metrics, review history shows a muted warning that the task-level choice applies to every task-derived metric. This reporting choice does not change task state, completion, history, assignment, or visibility. A separate exclusion on an individual recovered work run remains visible as run-level eligibility evidence; including the task again does not make that run eligible.

Understand continuation

A follow-up Coding-agent run and a returned Person run each retain a link to the reviewed run they continue. Use the work-run history selector or previous/next controls to inspect earlier attempts. A fresh Coding-agent run has no prior review continuation, even though both runs belong to the same task. This is why the task number is not enough to identify one execution: use the work-run history, or agent-facing CLI task commands, when you need to discuss a specific Coding-agent attempt.

For the live review actions, return to Review completed work.

History remains attached to the task after completion, reopening, Plan changes, closure, project-member removal, or coding-agent catalog changes. Missing facts on older runs remain unavailable instead of being inferred. Direct Person completion has no submission or review interval.