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

​
Lifecycle

Backlog

The task is created and waiting. No agent is running. Edit the title, description, or settings freely.

In Progress

A Claude agent spawns and begins working. The live terminal streams output in real-time. The smart timer tracks active coding time.

Testing

Claude has finished. The timer pauses. Review the changes — approve to mark done, or request changes to send Claude back to work.

Done

The task is complete. Token usage, duration, and logs are preserved for reference.

​
Task Fields

FieldDescription
TitleShort summary of the work
DescriptionDetailed instructions for Claude
Typefeature, bugfix, refactor, docs, test, chore
Priority0 (low) to 3 (urgent) — affects queue order
Modelopus, sonnet, or haiku
Thinking EffortControls Claude’s reasoning depth: low, medium, high

​
Model Selection

Best for complex, multi-file features. Highest token usage and cost, but strongest reasoning.

​
Priority Levels

When auto-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
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).