Skip to main content
The auto-queue system manages task execution so you don’t have to manually drag each task to In Progress. Enable it per project and Claude Board handles the rest.

​
How It Works

1

Enable auto-queue

Open project settings and toggle Auto-Queue on. Set the max concurrent agents (1–5).
2

Add tasks to backlog

Create tasks as usual. Each new backlog task is automatically considered for execution.
3

Tasks start automatically

When an agent slot is free, the highest-priority backlog task starts. If priorities are equal, the oldest task goes first.
4

Continuous processing

As tasks finish and move to Testing or Done, the next queued task starts automatically.

​
Priority Ordering

Tasks are picked from the backlog in this order:
  1. Priority — Urgent (3) → High (2) → Medium (1) → Low (0)
  2. Creation time — older tasks first (FIFO within same priority)
Set urgent priority on critical bugfixes to jump the queue ahead of feature work.

​
Max Concurrent Agents

SettingUse Case
1Sequential execution. Safe for projects where tasks might touch the same files.
2–3Balanced. Good for projects with independent modules.
4–5Maximum throughput. Best when tasks target different areas of the codebase.
Higher concurrency increases API costs and may cause git conflicts if agents edit overlapping files. Start with 1–2 and increase as needed.

​
Auto-Start on Task Creation

When auto-queue is enabled and agent slots are available, newly created tasks with backlog status are evaluated immediately. If the queue is empty and a slot is free, the task starts right away without manual intervention.

​
Disabling Auto-Queue

Toggle auto-queue off in project settings. Existing in-progress tasks continue running, but no new tasks will start automatically. You return to manual drag-and-drop control.