Adding Dependencies
Dependency Types
| Relationship | Display | Meaning |
|---|---|---|
| Waits for | Blue card with arrow | This task depends on the parent — it won’t start until the parent reaches done or testing |
| Blocks | Gray card | This task is a dependency of another task (read-only, shown for awareness) |
Cycle Detection
Claude Board prevents circular dependencies. If adding a dependency would create a cycle (A → B → C → A), the operation is rejected with a red warning:“Adding this dependency would create a cycle”The backend uses DFS (Depth-First Search) to trace the ancestor chain before allowing any new edge.
Dependency Patterns
- Chain
- Fan-out
- Fan-in
- Diamond
Sequential execution: A → B → C → D. Each task starts only after the previous one completes.
Queue Integration
When auto-queue is enabled, dependencies are enforced automatically:- A backlog task is only eligible to start if all parent dependencies have status
doneortesting - When a task completes, the queue immediately checks all its children — if their other parents are also complete, they start automatically
- This creates a cascade effect: completing one task can trigger a chain of dependent tasks
Planning Mode Integration
When using Planning Mode, Claude can generate dependency relationships between proposed tasks. Approved plans create tasks with proper DAG structure, ready for wave-based execution.API
Dependencies are managed through the Tauri IPC API:addDependency(taskId, dependsOnId)— Add a parent dependencyremoveDependency(taskId, dependsOnId)— Remove a dependencygetTaskDependencies(taskId)— Get parents and childrengetDependencyGraph(projectId)— Get full graph with edges and wavesgetExecutionWaves(projectId)— Get wave groupings