Skip to content

Work in the Task Workspace

Opening a task from anywhere lands you in the Task Workspace: one page that holds the spec, the work, the breakdown, and the conversation. This tour uses SUM-14, the offline maps task Rhea is working on.

You can reach it by short key. /app/tasks/SUM-14 resolves the same as the full identifier, which is why the docs quote keys.

The Overview tab of SUM-14, with the header, the run banner, and the details sidebar.

The header carries the title, the short-key badge, and two badges you can edit in place:

  • Status. Select it to pick another status. The workspace saves as soon as you choose, and a move the lifecycle does not allow comes back as an error rather than a silent no-op. See task lifecycle.
  • Priority. Low, normal, high, or urgent.

Under them, the origin badge says where the task came from (typed in by hand, merged from a meeting, or spawned by another task) and links back to it. Milestones at the right opens the execution timeline.

Below the header sits one banner with the single next action, chosen from the task’s actual state:

WhenThe banner saysThe action
An agent is runningAgent running, with the current step and budgetOpen execution
The agent paused for youAgent paused, needs youApprove or Reject
A run is under wayRun in progress, with the attempt countView run
The task is blockedWhat it is waiting onDiagnose
Nobody is on itNo one is working on this yetAssign
It is open or in progress, with nothing runningWhether the last run finished, or that it has not run yetReview run, or Open execution
It finishedWhether the last run was accepted or rejectedReview run

The only task without a banner is one parked in the backlog, which is the one state with nothing to do next.

The workspace opens on Execution when a run is live or the task is blocked, and on Overview otherwise, so the tab you land on is the one with the answer.

The spec and its metadata.

  • Summary is the task description, rendered from Markdown.
  • A typed panel appears above it for specialized types: a content task’s active child, a verification’s rubric, an approval’s proposed action.
  • The Details sidebar holds owner, assignee, created, updated, due, created by, project, meeting, and parent task. Assignee and due date are editable in place, the same way status is.
  • Advanced fields at the bottom is collapsed by default and holds the identifiers you need only when quoting the task to support.

Everything that has actually run.

The Execution tab of SUM-14, showing the run timeline as Rhea's agent works.

  • Runs, newest first, each with its status, its outcome once it has one, and its attempt count against the cap. Select one to open the run.
  • Agent run, when the task carries a step-by-step plan: the plan, its timeline, the budget spent against its cap, and any artifacts produced. A paused step gets Approve step and Reject step here.

A task nothing has executed says so rather than showing an error.

The child tasks of this one, with each child’s status, assignee, and due date. See subtasks and milestones.

The task’s conversation and history: comments from you, notes from agents, and the events that moved it. Use it to leave a correction an agent should read before its next attempt.