Understand the task workflow

A task is the durable project record for a piece of work. It can be worked more than once. Each attempt is a work run with its own queue attribution, agent output, review comments, and history.

1. Backlog is ready to organize or queue. Edit its details, then choose Queue when you want a coding agent to work on it.
2. Queued means a work run is waiting for a local listener. The task can show Awaiting local approval when a listener needs its operator to approve the selected command.
3. Agent working begins when a listener starts the coding-agent command. The task shows the active work and elapsed time.
4. Reviewing begins when the coding agent submits its change summary and AI hand-off. Open Review to inspect the result and decide what happens next.
5. Done means a reviewer marked the task complete. Its review history stays available.

Queueing and coding-agent completion change state automatically. Editing a task's content or metadata does not create a work run, unless the edit changes its state to Queued and you choose a coding agent. A reviewer can also create another run by requesting follow-up work or starting fresh work.

The task number, such as #12, identifies the task to people in its project. A work run is one execution of that task. A task can have more than one work run, and its review history shows each queued, started, and reviewed attempt.

Use Create and edit a task to prepare work, Queue a task to start an execution, and Review completed work to decide the outcome.