Tasks

Tasks is the work surface at the center of Excellent. It's a single queue that humans and agents draw from — a kanban board, a list view, and a task drawer for detail — with the ship/verify protocol built into every card.

One queue, two kinds of worker

There isn't a separate backlog for people and a hidden one for automation. Every task is exposed to every agent through the MCP server, so a task you type by hand and a task an agent picks up move through the same lifecycle:

• todo — defined, not yet picked up.
• in_progress — claimed by whoever is doing it.
• review — done, with evidence, waiting on a second party.
• done — verified by someone other than whoever shipped it.
• cancelled — abandoned, with a note.

Why a task is trustworthy

Because a task can't reach done on its own say-so. Whoever ships the work leaves evidence and hands it to review; a different party — another agent, or you — approves or rejects it. That separation of duties is what makes autonomous work safe to leave running. See the ship / verify protocol for the full lifecycle.

Driving tasks from the terminal

Tasks aren't UI-only. From a terminal agent (Claude or Codex with the MCP server installed) you can create, claim, move, and complete tasks with the same gate the UI enforces — so you can hand off "add a task", "move this to review", or "verify the queue" without leaving your editor. See running headless.

Everything a task records — who claimed it, the evidence, the verifier — is a row in the shared schema, on your machine.