Skip to main content
Every Task has one workflow status. Status controls where the Task appears; running state and Cogno ownership add treatments inside that status. Status does not control whether a Run may start or continue. Starting a Run preserves the Task’s status, and changing status does not stop a Run. Use the conversation’s stop control when you want to stop execution.

Visible statuses

The default query shows the four open statuses: status:backlog,ready,in_progress,in_review.

Hidden outcomes

Done, Archived, and Rejected columns start hidden on the Board. You can include them with the Board visibility control or a status: filter.

List and Board placement

On a computer, List shows In Progress first as one lane with a tab per person. The open tab lists that person’s running and waiting work, with Cogno-controlled work among it. The remaining sections follow In Review → Ready → Backlog. Cogno-controlled Tasks have no group or colour of their own; they are ordered and shown like any other Task. Execution ownership can also remain active in another workflow status. Board keeps every Task in its status column, Cogno-controlled cards included. On a phone, Tasks remain in their ordinary status sections.

Status proposals

After a completed run, Cogno can propose Backlog, Ready, or In Review and move the Task there with an open proposal. That move releases Cogno control. A failed or stopped Run does not determine the Task’s workflow status. Done remains a person’s decision; an ordinary agent result that asks for Done is folded into In Review. When a person explicitly accepts work in the Task conversation, the agent can apply that decision and move the Task to Done. Proposal metadata does not create a list lane or Board column. Use suggested:true to filter for Tasks with an unresolved proposal. Choosing a status deliberately resolves that metadata.

Reflect completion reported in Slack

Tell Cogno which work is finished in the original Slack thread, or include its Task link. Cogno checks the person’s statement against the existing Task and recent conversation before applying Done. A question, a partial result, a bot’s completion message, or an ambiguous match does not close the Task. No new Task is needed just to reflect completion. Moving a Task out of In Progress can cancel unfinished agent work. If the completion report concerns another Task still in progress, Cogno asks whether to stop and close it unless you have already made that decision explicit. When the Task’s own run records your decision, it applies after that run ends. Closing a parent also closes its sub-tasks, so the decision must cover all of them. Done hides the Task from the default open-work view without deleting it. Open its link or filter with status:done to find it again. To correct the decision, tell Cogno which Task to return to Ready, Backlog, or In Review. This does not restart cancelled work or reopen sub-tasks. The screen’s Undo for your own recent status change does not undo a change made by Cogno from Slack.

Transition rules

Filter aliases

Old saved filters continue to resolve to the current vocabulary: