Columns, modes and tags

A ticket is one unit of work for an agent. What happens to it along the way is told in How rev0 works; this page is the vocabulary.

Columns

The columns, in display order:

Column	What it holds
Backlog	Parked work. The runner never picks it up until someone moves it to To Do.
To Do	Queued for an agent. The runner claims tickets from here.
In Progress	An agent is working on it.
Pending Action	Needs you: a plan to sign off, a question, a tool request, a merge conflict.
In Review	The agent finished; the work waits for your review and, optionally, a merge.
Done	Signed off by a human. Only a human moves a ticket here.
Discarded	Dropped work, out of the active flow. The runner never picks it up.

A new ticket lands in To Do unless you pick Backlog in the Column field. The board default is Default column for new tickets in Settings > Workspace > New ticket defaults.

Ticket types

The Type field on the Create ticket form:

Type	What it is
Task	An agent runs it. The default.
Epic	No agent; it groups subtasks.
Command	Runs one skill or slash command, such as a repo report.
Loop	Runs a pipeline on a cron schedule. See Run a Loop.
Goal	A Loop that re-runs until its objective is met. See Loops and Goals.

A chat you start in Chats is a ticket too, of type chat. It stays off the board until you click Add to board at the top of it; from then on it is a card like any other, and the tickets it creates show on the board either way. See Ask in Chats instead of a ticket.

Modes

The Mode field decides whether the agent may start implementing straight away:

Mode in the UI	Value	What the agent does
Auto (agent executes freely)	auto	Implements, then finishes into In Review or asks for help. The default with the Developer and Maintainer profiles.
Plan (verbose text plan first)	plan_required	Writes a markdown plan with no edits, and stops in Pending Action for your sign-off.
Flow plan (visual behavior graph)	flow_plan	Same, with the plan as a behaviour graph of nodes.
Interactive plan (visual)	spa_plan	Same, with the plan as an interactive HTML page you annotate element by element. The default with the Explorer profile.

Accepting a plan switches the ticket to Auto: the plan is agreed, so from then on the agent is implementing rather than iterating on it. For a second plan inside the same ticket, pick a plan mode again (or ask the agent, which asks for the switch itself). Epics, Loops and Goals always run in Auto. The mode the Mode field starts on is Default mode for new tickets in Settings > Workspace > New ticket defaults, which the profile you chose at setup wrote (see Profiles); a board can override it. The plan type agents pick for themselves is Default plan type in Settings > Agents > Model & thinking.

Each ticket also has a Working directory (the repo the agent runs in; see Worktrees and branches), an optional Base branch, a Model and a Thinking level.

Tags

Some tags move a ticket when they are applied, so an agent can sort its own ticket with tag_ticket instead of an explicit status update:

Tag	Moves the ticket to
backlog	Backlog
claimed, in-progress, working	In Progress
plan-ready, needs-input, blocked	Pending Action
in-review, needs-review, review	In Review
done, completed	Done
discarded, discard, dropped, wontfix, wont-do	Discarded

Signing a ticket off renames its in-review tag to reviewed, and reopening the review renames it back, so a card never carries both. reviewed records what happened and moves nothing. Tags are normalized: lowercased, with spaces turned into hyphens.