Dependencies
Make a task wait until other tasks complete, and how plans create dependent tasks automatically.
A task's dependencies lists up to 100 task ids in the same organization. The task stays QUEUED until every
dependency is COMPLETED; the claim itself checks this atomically, so a task can never start early.
{
"projectId": "prj_123",
"title": "Show archived projects in the web app",
"prompt": "…",
"dependencies": ["tsk_api_archived_field"]
}Plans
A plan task proposes up to 30 tasks with dependencies between them. The plan is only accepted with unique keys, known dependencies and no cycles. Create N tasks creates them in dependency order, and they then wait for each other as usual.
When a dependency fails
If a dependency is FAILED or CANCELLED — or does not exist — the dependent task is blocked, and it shows the
reason, for example Dependency failed: tsk_…. Retry the dependency, or cancel the dependent task.
Dependencies are validated when the task is created: they must belong to the same organization, and a cycle is rejected.