Task Dependencies

This is a big one. Task dependencies bring full predecessor/successor relationships to t0ggles, letting you define exactly which tasks must finish before others can begin. No more guessing about task order or manually tracking what's blocking what.

#What You Can Do

• Define relationships - Mark tasks as "depends on" or "blocking" other tasks
• Visual editing in Gantt - Draw connections between tasks with drag-and-drop
• Task details management - Add and remove dependencies from any task
• Lag days support - Set gaps between dependent tasks
• Cycle detection - System prevents circular dependencies automatically

#Two Ways to Manage Dependencies

In Gantt View:

1. Switch to Gantt view
2. Click Edit Dependencies or press D
3. Click the right circle of a task and drag to its successor
4. Click any connection line to remove it
5. Press ESC to exit edit mode

In Task Details:

1. Open any task
2. Click the More menu (⋮)
3. Select Add Dependency
4. Search and select the task to link

Dependencies appear in a dedicated section showing both "Depends on" and "Blocking" relationships.

#API and MCP Support

Dependencies are fully supported in both the REST API and MCP server:

REST API:

• GET /api/v1/dependencies - List all dependencies
• POST /api/v1/dependencies - Create a dependency
• DELETE /api/v1/dependencies - Remove a dependency

MCP Tools:

• list-dependencies - View all task dependencies
• get-task-dependencies - Get predecessors and successors for a task
• create-dependency - Link tasks with optional lag days
• delete-dependency - Remove a task dependency

This means your AI assistants can now help manage task sequences and your custom integrations can automate dependency workflows.

#The Foundation of Serious Project Planning

Dependencies transform t0ggles from a task tracker into a full project management system. Without them, you're managing a list. With them, you're managing a workflow.

Think about any real project: design must finish before development starts, testing can't begin until features are built, deployment waits for QA sign-off. These aren't suggestions - they're hard constraints. Dependencies make them explicit and enforceable.

For agile teams, dependencies surface blockers before they derail a sprint. For product launches, they ensure nothing ships out of sequence. For client projects, they let you show stakeholders exactly why one delay affects everything downstream. Combined with the Gantt view, you can visualize your project's critical path and identify where delays will cascade.

Learn more in the:

• Task Dependencies documentation
• API documentation
• MCP Server documentation