Task Management in Workspace

Tasks represent the unit of intent in the workspace. A task captures what you are trying to accomplish, implementing a feature, fixing a bug, investigating behavior, or reviewing changes, before any execution begins.

The Task List

The left sidebar shows all tasks for the project under All Tasks. Each task displays a status icon, a truncated title, and a priority badge (Low, Medium, High, or Urgent).

Clicking the expand arrow on a task opens it inline in the sidebar, revealing:

• any chats associated with that task
• a + New Chat button to start a new session under the task directly

If a required integration is unavailable, for example, if a GitHub token has not been configured — a warning appears inline under the task.

Use the + button at the top of the sidebar to create a new task, or the search bar to find an existing one.

The Task Detail Panel

Selecting a task opens its detail panel in the right panel area. The header shows Task connected with an external link to open the task in the full Tasks view, and an unlink icon to disconnect the task from the current session.

The task detail panel shows:

Title and branch: the task name with a copy button, and the branch it is associated with.

Usage: token consumption and cost for this task (0 tokens, $0.00), and time tracked (0H).

Status and metadata chips: a row of attributes that can be set or updated:

• Status: for example, In Progress
• Priority: for example, Urgent
• Assignee: the team member responsible
• Attach: link files or references to the task
• Milestone: the milestone this task belongs to (for example, Pre-Launch Check)
• Cycle: the cycle it is part of (for example, Cycle 1)
• Estimate: time or effort estimate

Labels: one or more labels for categorization (for example, Code Quality). Labels can be added or removed directly from the panel.

+ Add subtask: add a sub-task directly from the detail panel without leaving the workspace.

Description: the task's objective in plain text. For example: "Dashboard components use untyped hardcoded data objects. Define proper interfaces to improve type safety and enable better IDE support."

Worktrees

The Worktrees section shows all worktrees associated with the task. A worktree is an isolated branch and sandbox created specifically to work on this task. Each worktree has its own execution environment, keeping work for this task separate from other tasks and the main branch.

Each worktree entry shows a creation timestamp and an external link to open it. A loading indicator appears while the worktree is being provisioned.

Comments

The Comments section shows discussion and notes left on the task. Comments are useful for capturing decisions, leaving guidance for future sessions, or coordinating between team members. They are visible to anyone working on the task but are not treated as executable instructions.

What a Task Is

A task defines the goal of work within a project. It describes the outcome you want, not how it should be achieved. A task exists independently of any single agent interaction — multiple execution attempts, approaches, and sessions can be explored under the same task without losing the original intent.

Tasks separate:

• what needs to be done (the task)
• how it is attempted (worktrees and sessions)
• the conversational execution (sessions)

When to Use Tasks

Tasks are best used when work spans multiple steps or iterations, you expect to try more than one approach, collaboration or handoff is involved, or traceability matters.

Creating or modifying a task does not execute any code or trigger agent actions. Tasks define intent and organization. All execution occurs through sessions and remains governed by project settings and permissions.