Related Tasks, subtasks and AI chats

Keep the work connected

Open a Task's Work and sessions area to connect related Tasks and the AI chats working on them. These links add context without changing the owner, deadline or completion state of the work.

Split only when the pieces need their own tracking

Use a checklist for steps that share one owner and deadline. Choose Add subtask when a piece needs its own owner, date, status or completion evidence. A subtask is an ordinary Task: it can finish or become blocked independently, and finishing it does not automatically finish its parent.

Enter a deadline when the child needs a different date. If you leave it empty, it inherits the parent's date. Check the created Task before continuing.

Link existing work

Choose Link work instead of creating a duplicate Task. Use:

• Part of for a piece of a larger result;
• Depends on when work needs another Task to finish;
• Related to for useful context without an ordering requirement.

The linked Task retains its own status and owner. A relationship is not a grant of access to another company's records.

Keep an AI chat with its Task

Choose Link chat to associate an existing chat you own. One Task can have several chats, and one chat can contribute to several Tasks. Linking a chat does not start an agent, resume a conversation, invite participants or share its private content.

Read execution state separately from Task state. A queued, waiting, failed or finished chat describes the execution, not whether the customer or business outcome has been achieved. Keep the next action, evidence and any remaining blocker on the Task.

Read usage correctly

A chat's session-token total is not automatically the usage charged to every linked Task. Task-attributed usage and cost depend on the available execution records. Missing, partial or stale usage remains labelled rather than treated as zero.

Tasks holds the work. Planning holds the measurable goal. Calendar holds the time commitment.