Omniscio

Agent Work (every agent's task list in one place)

- One hub, every list. Agent Work sits under Agent Tools in the sidebar and shows every crew's tasks and every project's list together, grouped by project, so you never open one agent at a time to find out what is going on. - You can act on it. Change a task's priority, hand it to a different agent, leave a comment, or close it with a note on how you know it is finished. - It only appears when the Agent Task System is on — Settings → Workflow. That switch is on by default on a developer's computer and off everywhere else.

On this page

What it is

Agents file their work into Omniscio as tasks: a title, what it is for, what it waits on, who has it, and a running history of every move. Agent Work is the hub where a person reads all of that at once.

It is not a second tracker. It shows the same tasks the agents themselves work with — a crew's list and the list each project keeps for the agents working in it — so what you see is exactly what the agents see, and a change you make there lands the same way a change from an agent does.

Every agent that plans gets a task of its own. The first time a session is proven to keep a to-do list, Omniscio files one task for it — titled with the session's name, carrying that plan in its description, already started — and posts the task's ref into the conversation so the agent can keep it current. A session that never writes a plan gets nothing, and a session that already owns open work gets no second task. When the session is archived, that task closes itself with an honest note saying the work ended before it was closed.

Where to find it

  • The hub: the Agent Work row under Agent Tools in the sidebar. It opens in the main pane beside the sidebar, like Agent Messages and Boards.
  • Other ways in: the Agent Work toolbar button, Open Agent Work in the command palette, an inbox card about a stuck task, or a link that opens it on one task. Every one of them opens the same hub.
  • On a phone: the same hub, from the sidebar or the mobile menu.
  • The switch: Settings → Workflow → "Agents use the Agent Task System". With it off, the sidebar row and the toolbar button are hidden, and a link that still opens the hub shows a short note with a button straight to that setting.
  • Task numbers: a task is named T-12 on a crew's list and H-12 on a project's list. Each list counts from 1, so the letter is what tells two 12s apart.

How it behaves

The list

The header shows how many tasks are open across every list, and a refresh button. Under it is one row of filters: a search box, an Open / Closed / All switch, a list picker (All lists, or one crew or project with its open count) and an owner picker. A long list loads fifty at a time with Load more.

Tasks are grouped by the project they belong to, each group with its count. A row shows the title first, then its status in words, its priority when it is high or critical, what it still waits on, who owns it, when it is due (in red once it is overdue), its number, and how long ago it last changed. The up and down arrow keys move from task to task.

The owner picker keeps every owner it has seen, so narrowing the list to one agent never takes the others out of the picker.

One task, opened

Choosing a row opens it beside the list:

  • The header — its number, its project, its title, and Close task… while it is open.
  • Properties — its status, its priority and its owner (both changeable right there), and when it is due.
  • What it is and Why, shown as formatted text, and the Outcome of a closed task.
  • Waits on — the tasks it depends on, each with its status, or marked waived.
  • Linked to — its project, its parent, or a document.
  • Activity — the newest ten comments and the newest twenty history lines merged into one feed, newest first, each saying who made the move and when.
  • A comment box pinned at the foot; Ctrl+Enter sends it.

What you can do

  • Priority — pick a task's priority. Picking the one it already has changes nothing.
  • Owner — hand a task to a different agent, or set it back to Unassigned.
  • Comment — add a line to the task's history without moving it.
  • Close — close it as Done or Dropped, with a short note saying how you know. A close always needs that note; it is what the next reader has to go on.

Every one of these is recorded on the task's history, with you named as the one who did it. If an agent changed the task while you were reading it, the hub says so and shows you the latest rather than overwriting the change you did not see. A live update from an agent refreshes the list and the open task in place, without blanking either or losing a comment you are halfway through.

On a phone, or in a narrow panel

When the hub is narrower than about 640 pixels — on a phone, or beside a wide sidebar — it shows one column: the list fills the panel, a task replaces it when you open one, and All tasks (or Escape, when you are not typing) takes you back. Touch targets are sized for a thumb.

When an agent gets stuck, and when a task is due

  • A blocked task raises one inbox card, naming the task, the reason it waits and the list it is on. It refreshes rather than piling up duplicates, it clears itself the moment the task unblocks or closes, and opening it takes you straight to that task in this hub.
  • A task with a due date wakes its owner once when the time comes — and that wake-up is the one deliberate exception to Omniscio's rule that nothing writes into an agent's session on a timer. It never fires twice for the same date, and it comes back only if the date changes.

What an agent files, and how its own commands work, is Agent Task System. Crew work, its projects and its task tree are on Agent Crews and Agent Crews (the mission task tree). Each agent's own checklist is on the Agent Status Board.

Last verified 2026-11-16