Review and recover task work

When a coding agent submits a work run, the task enters Reviewing. Open Review from the task to read the change summary, inspect any linked code review, and verify the local Git changes against the task details. The AI hand-off describes the completed work and where the agent stopped so a future coding agent can continue if you request more work. The resolved coding-agent command is also available for reference.

Open a Reviewing task to enter its visually distinct Review workspace and inspect the change summary, AI hand-off, code-review link, command, and review comments. A prominent purple review header carries the Review workspace label and review icon, distinguishing this decision point from ordinary task details before you begin reading. You can then:

• Mark done to accept the current result.
• Request follow-up work after adding at least one review comment. The selected coding agent receives the review continuation.
• Start fresh to choose a coding agent and queue a clean, unlinked run. The reviewed run stays in review history, but its feedback is not continuation context for the new run. The new work-run context explicitly tells the coding agent to restart from the current task details and general comments instead of prior review or agent output.

Current review comments can be edited or deleted by their author and by people with project moderation permission. Follow-up work requires a completed review run with a change summary and AI hand-off, plus at least one review comment; it then receives the prior summary, AI hand-off, and current review feedback. Both follow-up work and Start fresh ask you to choose a coding agent and move the task to Queued.

If a task was moved to Reviewing without a completed work run, Start fresh still queues a clean run.

Open the task details while it is in Agent working and find Recover agent work beneath the task header. Use this section when a coding-agent process stopped, when it finished without submitting its work, or when you moved a task directly to Agent working and now want alterac.ai to queue it. The section remains available whether or not a listener or active work-run record exists:

• Start fresh: choose a coding agent and queue a clean run without prior-run linkage or a continuation comment. If an incomplete run exists, alterac.ai removes it from visible history. The replacement receives an explicit fresh-start instruction and should rely only on the task's current details and general comments.
• Requeue and continue: choose whether the agent completed work without submitting it, its terminal closed before completion, or something else happened. Add a custom description for the third choice, choose a coding agent, and queue a run that receives the selected recovery details. If an incomplete run exists, alterac.ai retains it as continued after a problem and links the replacement to it. Use this when the next agent needs to know what happened or what useful work to preserve.

The selected recovery details are saved as a continuation comment with the task and included when the replacement run starts. A retained run marked Continued after a problem shows who recovered it and when. It is excluded from duration, concurrency, and other work-run metrics. If the task has no work-run record because its state was changed directly, there is no old run to remove, retain, link, or exclude; the difference is whether the replacement receives a continuation comment.

Late output from the replaced run is rejected, so it cannot move the task into review or overwrite the replacement run.

Both recovery paths require an explicit coding-agent selection. Review the command preview and every selector before confirming. alterac.ai does not automatically reuse the previous run's coding agent or selector choices.

If the task or active-run presence changed after you opened the dialog, refresh the task and repeat the action against the current state.

Use complete your first task for the full first-run path, including the listener and queueing steps.