tasks

You can orchestrate tasks across multiple sessions in Gobby by using the gobby-tasks MCP server to create, update, and track tasks with dependencies. It requires retrieving tool schemas once per session and using the session_id from the SessionStart context to coordinate workflows.

The best way to expand an epic into subtasks within a workflow is to use the task expansion command to break down epics, manage dependencies, and coordinate across sessions to keep work aligned. You provide the task ID and any needed session_id to generate structured subtasks.

Yes, you can track task dependencies and validate work using the gobby-tasks MCP server. It supports built-in validation mechanisms and allows you to manage dependencies, ensuring that work is validated and tasks are only executed when their dependency requirements are met.

To create and list tasks with structured fields, you use standardized fields such as title, description, status, priority, labels, and dependencies. You can create a new task within your current session and then run a list command to view, track, and manage these tasks efficiently.

Yes, Gobby task orchestration requires a session_id to function properly. You must retrieve the tool schemas once per session using get_tool_schema and provide the session_id from the SessionStart context to successfully create, update, and track tasks across different sessions.

Gobby tasks may not update across different sessions if the session_id from the SessionStart context is missing or incorrect. You must retrieve the tool schemas once per session using get_tool_schema to ensure the MCP server can properly orchestrate and synchronize task updates.