Tasks are work-orders

A task in Claos isn't a checkbox; it's a work-order. It captures who's doing the work, the spec, the schedule, and the trail of what got done — and the same task shape covers both human and AI assignments.

This article walks through every field on a task, what changes when an agent is the assignee, and how the comment thread becomes the audit trail of the work.

A task is a work-order

Most of the work in Claos comes from delegating tasks to agents or teams. The human-assigned case still works — you can put a task on a teammate's plate the same way — but the centre of gravity is delegated work. A task is the unit you hand off.

Every task has a title, a status, a priority, an assignee, and a description. The fields that show up after that depend on who you're handing it to.

Opening a task

Two ways to open one:

Slide-over panel — click a task on the Board, Table, Timeline, or Calendar view. The detail opens on the right.
Full page — click the expand icon in the slide-over, or use the task's URL directly.

The fields, in order

These are the fields you'll fill in, top to bottom:

Title. Required. Edit inline.
Status. Dropdown of the statuses you configured in the project (see What a project is). Pick where the task is in its lifecycle.
Priority. Urgent, High, Medium, or Low. Defaults to Medium. Workspace-wide — same four options on every task.
Assignee. Opens a picker with three groups: People, AI Agents, and AI Teams. A task has one assignee — a person, an agent, or a team, never a mix.
Due date. Date picker. Hidden when the assignee is an agent or team — AI tasks use the AI Schedule fields instead. We'll come back to this in a moment.
Labels. Multi-select from workspace-scoped labels — each label has a name and a colour. You can create a new label inline from the picker.
Description. Rich-text editor with a slash menu, code blocks, callouts, pasted images. The agent reads this when running the task, so be specific about what you want.

When the assignee is an agent or a team

Picking an agent or team changes the task in two ways:

The Due date field disappears.
An AI Schedule section appears in its place, with Frequency, Time, and Days controls — Run now, Run once, Hourly, Daily, Weekdays, Weekly, or Monthly.

The schedule is what tells the agent when to run, so a due date would be redundant. The full mechanic — how each frequency reads, the worked examples, what lands in your inbox — is documented in Putting an agent on a task and Scheduling an agent.

Subtasks

A task can carry subtasks — smaller checklist items underneath the main one. Click Add subtask to create one inline, give it a title, and check it off when it's done. Subtasks have their own descriptions if you need to spell something out further; expand a subtask to write in its body.

A progress bar at the top of the subtask list shows how many are complete. Subtasks are scoped to the task they're under — they don't appear in the project's main views.

Comments and the audit trail

Below the description, the comment thread. Add a comment, @mention a teammate to notify them.

This is where the task becomes the trail of what was done. When an agent runs against the task, the agent posts back here — what tools it called, what it produced, the final reply. Scroll the comments to see the work. For the full run timeline — tool inputs and outputs, step-by-step — click through to the agent or team's chat (see Reading agent runs and Reading team runs).

Tips and gotchas

One assignee per task. Pick a person or an agent or a team. The "agent drafts, human reviews" pattern is two linked tasks, not two assignees on one.
The due date is hidden on AI tasks because the AI Schedule replaces it — the cadence already says when the work runs.
Be specific in the description. Agents read it as the brief. Vague descriptions produce vague output; "Draft a 200-word LinkedIn update for the launch, tone matching the brand voice doc, no exclamations" produces something usable.
Reassigning between human and AI works. Switching a task's assignee from a human to an agent reveals the AI Schedule; switching back hides it and restores the due date. The task itself doesn't get reset — comments and subtasks stay.