# Tasks

Tasks are user-created work orders for one or more connected Agents. They stay separate from Sessions: normal Agent use creates a Session record, while a Task exists only after a user defines work and assigns it.

## Create a Task

Create a task from **Dashboard → Tasks**, a Session compilation, or a long-term memory. A task keeps its title, instructions, source context, assigned Agents, execution strategy, results, attachments, and history on one canvas.

Use a Session or memory as context when it helps an Agent begin with verified information. The original source remains linked for review.

## Assign Agents

Choose one or more online endpoints and an execution mode:

| Mode | Behavior |
|---|---|
| Notify | Delivers the work order for later handling |
| Confirm | The endpoint accepts the task before execution begins |
| Automatic | A healthy endpoint starts an isolated Agent run and reports its result |

Each assigned Agent receives its own execution step. Their results appear together on the same task canvas, so parallel work never creates duplicate tasks.

## Task Lifecycle

| State | Meaning |
|---|---|
| Pending assignment | The task has no active execution target |
| Delivered | TokST sent the task to a selected endpoint |
| Accepted | An Agent accepted the work order |
| Executing | The Agent is running and reporting activity |
| Review required | A result needs user or workspace review |
| Completed | The result is saved on the task canvas |
| Archived | The task remains available as history |

The timeline records creation, delivery, acceptance, executor start, first activity, tool activity, saved result, and follow-up processing with millisecond timestamps.

## Results and Context

Task results are persisted before background session organization and memory extraction. A completed task therefore remains readable even when later background work needs attention.

Use Session records for automatic capture and long-term Memories for reusable facts. A task can cite either source, while its execution result remains part of the task history.

## Controls and Recovery

Owners and Admins can reassign, archive, delete, or review tasks within their workspace permissions. Isolated read-only work can retry once on a healthy endpoint after a transient failure. Tasks that can change a project, file, or external system retain their diagnostics and require an explicit user decision before reassignment.

Use **Dashboard → Tasks** to filter pending, running, accepted, review-required, completed, and archived tasks. The Agent page shows endpoint availability, active model, recent activity, and execution health before assignment.