Tasks are the core unit of work in Claude Board. Each task represents a job for a Claude agent to complete.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.
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.
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
- Opus
- Sonnet
- Haiku
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