Tasks

The task board tracks durable work across manual tasks, delegated work, imports, structured-session emissions, and schedule-created runs.

Statuses

StatusMeaning
BacklogCreated but not queued yet
QueuedReady to run
RunningActively executing
CompletedFinished successfully
FailedEnded with an error
CancelledIntentionally stopped before completion
DeferredIntentionally postponed with a recorded reason
ArchivedRemoved from the live board but retained for history

Approvals can affect how a task proceeds, but approval is not a task status. Approval waits show up in the task/chat runtime while the task remains in its normal operational state.

Where Tasks Come From

  • manual task creation
  • agent-created tasks via platform tools
  • delegation to another agent
  • schedule-origin work
  • GitHub issue import
  • structured sessions that emit follow-up tasks

Task Shape

Tasks can carry more than a title and status:

  • assigned agent
  • project and goal linkage
  • task dependencies (blockedBy / blocks)
  • source metadata (manual, delegation, schedule, import)
  • upstream results from completed dependencies
  • artifacts, output files, comments, and verification summaries

Delegated Tasks

Agents with delegation enabled can create delegated tasks for other agents.

Delegated tasks:

  • are assigned to the target agent
  • keep origin metadata
  • can be restricted to selected delegate targets
  • can continue routing follow-ups back to the originating connector or session when configured

Approval Workflow

When capability policy requires approval, a running task can pause before a sensitive tool execution step.

Inline approvals can appear in the chat and task surfaces. Once approved, the normal task and session runtime resumes.

Schedule-Origin Tasks

When schedules fire, they create schedule-origin tasks.

Important behavior:

  • execution targets are stored explicitly
  • schedule runs do not guess from the most recently active chat
  • archiving a schedule can cancel linked queued or running tasks
  • cancelling an in-flight schedule task can abort its active structured session or run cleanly

Dependencies and Pool Mode

Tasks can model lightweight execution planning:

  • dependency edges through blockedBy
  • pool-mode claiming for eligible agents
  • result propagation from completed dependencies into newly unblocked work

This keeps the task board usable both for manual operators and for agent-driven work routing.