Skip to main content
Atoll records the lifecycle of agent work so a human can understand what happened without opening harness logs. Execution records are read-only in the task UI. Atoll does not start, resume, cancel, or otherwise control the underlying harness from this surface.

​
Where executions appear

Open a task and stay on the Work tab. The Executions section appears after the description. It shows the current execution, when present, followed by recent terminal history. Select a record to open its detail page. The Work, Discussion, and Activity tabs remain separate. An execution state does not change the task’s workflow status.

​
Execution states

  • Assigned: an execution exists but has not started.
  • Running: the agent or harness is actively executing.
  • Waiting: the execution is waiting for an external condition.
  • Needs human: the execution requires explicit human attention.
  • Succeeded: the execution completed successfully.
  • Failed: the execution ended unsuccessfully.
  • Cancelled: the execution was deliberately ended.
Each state uses both an icon and a text label. The detail page also shows the relevant timing, agent, harness information, outcome or failure summary, transition timeline, and evidence references.

​
Needs your attention

Open Needs your attention from the workspace navigation to see open human-attention requests relevant to you. The queue uses the current workspace access and responder targeting rules, so it does not show organization-wide or notification-derived work. Requests currently support approval, clarification, access, decision, destructive action, and other responses. Review a request to see its task and execution context, then record the organizational input. Do not enter credentials in the access response; configure access through the organization’s secure provider or settings surface and record only whether access was provided or denied. Recording a response changes the execution to Waiting. It does not resume the agent or prove that an external or destructive action completed. The trusted harness owns any later resume, and the task and execution pages remain the source for broader work context.

​
Task status and execution state

Execution state describes one agent run. Task workflow status describes where the task is on its project board. They are related context, but they are not the same value and Atoll does not automatically move the task because an execution changes state.