How Agently Works

Work

Work is the single queue for everything happening in your workspace. Tasks you hand Jarvis, tasks your teammates create, tasks a Routine fires on a schedule, and tasks Jarvis creates for itself while working all land here. It is the screen you spend the most time on.

There is one idea behind it: a task is a briefing, not a sticky note. What you write in the task is what gets handed to the agent when it runs. So the board is not a record of work happening elsewhere. It is the work.

Coming from an older version? Work replaced the separate Command Center and Spaces screens in August 2026. Both URL families now redirect here. Everything you could do on them, you do on Work.

Starting a task

Click New task in the sidebar, or press ⌘N. Your workspace home is the same composer, so an empty workspace opens straight into it.

Describe the outcome you want in plain language. You do not pick an agent or a category. Jarvis reads the brief, pulls what it needs from your Brain, and works the problem.

In the composer you can:

  • Attach files the agent should read.
  • Type @ to pull a Page, a Brain item, or another task in as context.
  • Type / to run a Skill by name.

Once it starts, the task appears in the queue and streams its progress. You can leave. It keeps going.

The three lenses

The same tasks, drawn three ways. Switch with the lens control at the top of the screen.

List

The default. Tasks grouped by what you should do about them, in the order you should care:

Needs you · Running · Today · This week · Done today · Done earlier

"Needs you" is the only group that is ever urgent. Everything above the fold is either waiting on a decision from you or actively moving.

Board

The same tasks as columns, for when you want the shape of the week rather than the order of it:

Queued · Running · Needs someone · Done today

Drag a card between columns to change its state. "Needs someone" is the board's name for a task that is blocked on a human, whether that is you or a teammate.

Canvas

A spatial view of the queue, for planning. Useful when you are laying out a project and want to see how pieces relate rather than reading them as a list.

All three lenses share one filter: Mine or All. Mine shows tasks assigned to you, All shows the whole workspace.

What happens when a task runs

A running task is not a spinner. You can open it and watch:

  • The step timeline. Every tool call the agent makes appears as its own row: searching the Brain, reading a web page, drafting an email, updating a record.
  • Delegation. When Jarvis hands a heavy chunk to a specialist sub-agent, you see that happen too.
  • Citations. Facts pulled from your Brain show the source they came from.

Several tasks run at once, each streaming independently. Work is a queue, not a single conversation.

Review, re-run, ship

When a task finishes, it moves to a state that needs your eye rather than straight to done. From there you can:

  • Leave feedback and run it again. Your notes go into the next run as context. This is the loop that turns a good-enough first draft into the thing you actually wanted.
  • Ship it. Accept the result and close the task.

Because the brief and every revision stay on the task, you can reopen it weeks later and run it again with fresh data. That is the difference between a task and a chat you have lost.

Tasks that need a person

Some tasks stop and wait. Two reasons:

  1. The agent needs an answer. A missing detail, an ambiguous instruction, a choice only you can make.
  2. The action needs sign-off. For work running unattended, sensitive actions get proposed rather than executed. Those land in Approvals.

Either way the task shows up under Needs you until it is resolved.

Asking Jarvis to manage the queue

Jarvis can read and write the queue itself, so you can direct it in the same breath as the work:

  • "Create a follow-up task for the Acme renewal, due Friday."
  • "What is blocked right now and who is it waiting on?"
  • "Set up the Q2 launch: break it into tasks with owners and dates."

Tasks it creates behave exactly like tasks you create, and your team sees them immediately.

← Meet JarvisRoutines →