Work: what your agents are doing

Last reviewed: 16 Sep 2026

The Work page is where you read what your agents are doing without reading a chat. Agents open jobs as they take things on; each job carries a spec, todos and a work log. The page shows the jobs that are moving, the ones waiting on you, and the ones going quiet.


The bands, top to bottom

  • Who's here. Every agent window active on this project right now, what each is on, and what it did this session. Live now means it did something in the last fifteen minutes; idle means it is connected and waiting. Earlier folds the windows from the last week that are gone now, so you can find the chat that did the work.
  • In motion. Jobs an agent is on now, or touched today. A job earns a card by moving; everything else folds into the bands below. Read the card: the spec, the todos ticked, the last update.
  • Needs you. Jobs an agent could not finish without you: a blocker it named, a decision it is waiting on, or a disputed entry only you can settle. Everything else keeps moving without you; this band is the whole list of where it does not.
  • Quiet. Started jobs nobody has touched for under a week and nobody is on. Not a problem yet.
  • Stale. Started jobs untouched for seven days or more. Finish them, hand them to an agent, or archive them; a long stale list hides what matters.
  • Not started. Draft jobs, waiting to be picked up.
  • Completed. Done jobs, newest first, with when they finished. Anything finished in the last day is marked new.
  • Git activity. Pushes from a linked repository, so you see the code move next to the work. Connect a repository from the Connect page.

The Plan toggle at the top shows the project's roadmap instead: Now, Next, Later, and what shipped.


What a job is

One piece of work an agent can plan, build and finish, usually in a day or three. It has:

  • a spec (what, why, edge cases, how we know it is done), which the agent writes before building;
  • todos, ticked as it goes;
  • updates, the work log: what changed and what is next, with the files and commits attached;
  • a status: draft, planning, building, reviewing, done.

Two rules protect the outcome. A job does not move to building on a thin spec. And a job does not close without a closing note and either an understanding commit or an honest "nothing durable came out of this".

How to use it

Look at Needs you first; it is short by design. Then In motion for what changed. Open a card rather than a chat: the spec, the ticked todos and the last update tell the story. If a job in Stale still matters, say "pick up job where it left off" to an agent.