> ## Documentation Index
> Fetch the complete documentation index at: https://docs.claboard.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Tasks

> Task lifecycle, fields, and configuration

Tasks are the core unit of work in Claude Board. Each task represents a job for a Claude agent to complete.

## Lifecycle

<Steps>
  <Step title="Backlog" icon="inbox">
    The task is created and waiting. No agent is running. Edit the title, description, or settings freely.
  </Step>

  <Step title="In Progress" icon="play">
    A Claude agent spawns and begins working. The live terminal streams output in real-time. The smart timer tracks active coding time.
  </Step>

  <Step title="Testing" icon="flask">
    Claude has finished. The timer pauses. Review the changes — approve to mark done, or request changes to send Claude back to work.
  </Step>

  <Step title="Done" icon="check">
    The task is complete. Token usage, duration, and logs are preserved for reference.
  </Step>
</Steps>

## Task Fields

| Field               | Description                                                |
| ------------------- | ---------------------------------------------------------- |
| **Title**           | Short summary of the work                                  |
| **Description**     | Detailed instructions for Claude                           |
| **Type**            | `feature`, `bugfix`, `refactor`, `docs`, `test`, `chore`   |
| **Priority**        | 0 (low) to 3 (urgent) — affects queue order                |
| **Model**           | `opus`, `sonnet`, or `haiku`                               |
| **Thinking Effort** | Controls Claude's reasoning depth: `low`, `medium`, `high` |

## Model Selection

<Tabs>
  <Tab title="Opus">
    Best for complex, multi-file features. Highest token usage and cost, but strongest reasoning.
  </Tab>

  <Tab title="Sonnet">
    Balanced choice for most tasks. Good reasoning with moderate cost. **Recommended default.**
  </Tab>

  <Tab title="Haiku">
    Fast and cheap. Use for simple fixes, docs updates, or boilerplate generation.
  </Tab>
</Tabs>

## Priority Levels

When [auto-queue](/features/queue) is enabled, higher-priority tasks start first:

* **Urgent (3)** — runs immediately if a slot is available
* **High (2)** — next in line
* **Medium (1)** — default
* **Low (0)** — runs last

<Tip>You can change a task's model, type, and priority while it is still in backlog. Once in progress, only the description can be updated (for revision feedback).</Tip>