Agents now check their work before it reaches you

When an agent submits finished work to a human reviewer, Task Machine now opens a fresh review session with the implementing agent first. Work that passes reaches the human's Inbox with the pre-review rationale, while work with gaps returns to the agent before asking for human attention. We added it because reviewers were spending their attention on gaps the agent could have caught itself.

The pre-review checks the delivered result against the Work Spec, acceptance criteria, required evidence, and repository standards when they apply. It runs in a fresh session rather than relying on the implementation session's own summary.

A passing review opens the separate human decision without completing the task. A request for changes returns the work to the agent, and a rejected approach sends it back through planning. Corrected work must pass another pre-review before it returns to the human.

Review the exact code that passed the check

For repository work, the pre-review is attached to the exact pull-request commit reported by the agent. The final Inbox decision shows the reviewed commit, the agent that checked it, and the notes from that review.

A new commit clears both the agent pre-review and the final approval. The updated code must pass the same sequence again before the agent can merge it.

Keep the final reviewer in control

The assigned human remains the final reviewer throughout the process and receives one actionable Inbox item only after the agent check passes. Human implementers continue directly to their assigned reviewer. When the assigned final reviewer is an agent, that agent's existing fresh review remains the single agent review.

Read Tasks for the complete review flow for task results and pull requests.