Tasks

Tasks give agent work a place to start and a record to come back to.

Use the Tasks surface when work needs more than a prompt: description, assignee, labels, workflow state, implementation plans, session logs, and review context.

Set up a task board

If Tasks is not set up, Coldtea offers a Coldtea task board setup flow and, where available, an import path from Linear. The exact choices depend on your team and integrations.

A task board belongs to a TeaHouse and team. If you are looking at the wrong board, switch the TeaHouse or team before creating work.

Board view

The task board supports list and board layouts. Use the toolbar to search, filter by workflow state, labels, or assignee, and switch the view mode.

You can drag tasks between workflow states. That updates the task's state; it does not prove the code is done. Keep workflow moves tied to review and checks, not optimism.

When a board gets large, Coldtea keeps the list responsive by windowing rows. That should not change how you use it, but it explains why very large boards still scroll normally.

Task details

A task detail page includes:

• Editable title and description.
• Parent and subtask context.
• Workflow state, priority, assignee, and labels.
• Activity.
• Session logs.
• Implementation plans.

Use the description for intent and constraints. Use plans for the route. Use logs for what actually happened.

Start work from a task

The Get to work panel can start local agent work from the task. Choose the agent, choose the project, then decide whether to open in a worktree.

For multiple selected tasks, Coldtea prefers worktrees because separate tasks usually need separate branches. Still check the generated worktree names and base branch before launching.

Where cloud runs are enabled, the same panel may offer local and cloud run modes. Cloud runs can require GitHub setup, repository access, and credentials before they are ready.

Session logs and plans

Task-linked brews can leave session logs and implementation plans on the task. Read them before continuing old work or reviewing a diff.

A useful log says what changed, what failed, what checks ran, and what remains. If a log only says “done,” treat it as a weak signal and inspect the diff yourself.

When not to use Tasks

Skip Tasks for throwaway local work:

• Explaining a file.
• Trying a command.
• Asking an agent to inspect something before you know the actual task.

Once work needs a branch, a review, or a teammate's attention, put it in a task.

Next: use tasks or read the tasks, plans, and logs model.