Guides
Use dependencies
Create dependencies between jobs to control execution order.
Use dependencies to make one job wait for another before it can start.
Add a dependency
- Open the job that should wait (the dependent job).
- In the job detail panel, find the Dependencies section.
- Click Add Dependency.
- Search for the job it depends on and select it.
- The dependency is created immediately.
The dependent job cannot move to Ready until all its dependencies are Done. You see a list of blocking jobs in the job detail panel.
Remove a dependency
- Open the dependent job.
- In the Dependencies section, find the dependency you want to remove.
- Click the remove button next to it.
The job is no longer blocked by that dependency.
View the dependency graph
Coord visualizes dependencies as a graph where each job is a node and dependencies are connections between them.
- Open the dependency view from the workspace sidebar or job detail panel.
- Each node is color-coded by its state — you can see at a glance which jobs are done, running, or blocked.
The graph is read-only. Use it to understand the structure of your work and identify bottlenecks.
Rules and constraints
- Dependencies can only be added to jobs in the Backlog. Once a job has moved past the Backlog, its dependencies are locked.
- A job can have multiple dependencies. All must be Done before it can become Ready.
- Dependencies work for both agentic and user jobs.
- Circular dependencies are prevented. If adding a dependency would create a cycle, Coord blocks it.
- Removing a dependency from a job in the Backlog that now has all its dependencies satisfied does not automatically move it to Ready — you still move it manually.
Example: sequencing a pipeline
Suppose you have three jobs:
- Write tests (user job) — a person writes test cases.
- Implement feature (agentic job) — an agent implements the feature based on the test cases.
- Deploy (agentic job) — an agent deploys the changes.
Set up dependencies: Implement depends on Write tests. Deploy depends on Implement. Now each job starts only after the previous one is done.
Next steps
- Dependencies — concept reference
- Create your first job — create jobs to connect with dependencies