Retain / User Guide
Back to User Guide
Productivity

The Work list

Invalid Date
4 min read

The Work list is one list of everything you have in flight: the build packets your agent is working through, the documents Retain is writing for you, and the work you linked to a Thread. Open it to see what needs you, what is running and what has gone quiet, then put finished work away. It is Work in the Mac sidebar and the Work tab on iPhone, with the same rows on both.

What is on it

A row is on the list because you are in the middle of it, not because it exists. Everything else stays reachable by search.

  • Build packets. A build packet is one change to your code, from the reason for it to the pull request that ships it. Packets you started from a meeting, packets your agent designed, and OpenSpec changes your agent synced from a repository all appear here.
  • Drafts and documents. Emails, design docs, notebooks and the other documents Retain writes for you. A plan, the steps Retain lays out for one of your tasks, shares a row with its documents.
  • Linked work. A checklist or change you linked to a Thread. The row names the Thread and how many tasks are done, and opening it opens the Thread. See Closing the loop on a thread.

How it is grouped

Under All, rows sit in sections, each listing its newest change first.

  • Needs you. Work is stopped until you act, something failed, or something finished that you have not looked at yet.
  • Working. Retain or your agent is doing something now.
  • In progress. Nothing to flag, and something changed in the last two weeks.
  • Quiet. Nothing has changed for two weeks.
  • Archived. Work you archived or sent, and packets you dropped. It is not part of All; choose it to see it.

On the Mac, the All menu above the list switches between sections, each with its count, and a section's header folds. On iPhone a row of chips does the same. Both have a search field. The Mac sidebar counts the rows in Needs you, and the Work tab on iPhone shows a dot while something waits on you.

What a row says

Each row shows its title, its Thread, a status, its kind and when it last changed. A row has at most one status, and the first that applies wins: Needs you, Failed, Ready or Working. A row with nothing to say has no mark.

The words beside the mark say why, for example "Building 12 of 25", "Built", "Draft ready", "Run failed" or "Shipped. Mark done?". Progress that is not a status, such as "3 of 25 tasks", appears as plain text. Ready clears once you open the work, on any of your devices.

To see what a packet depends on, open its Build tab. See The Build tab.

Put work away

Choose Archive from a row's menu on the Mac, or swipe the row on iPhone. If the row has an open task, Retain asks "Archive and mark done?", because archiving completes the task. Archived work stays readable under Archived. Unarchive brings it back, and so does reopening its task.

Retain also clears work when the evidence is plain: a draft was sent, or its task was closed elsewhere. It never deletes anything. Linked work that reports itself finished waits for you instead, with Mark Done in its menu.

Go through it with your agent

Run /retain:curate-work in a checkout of your repository. Your agent says how many Working packets are in this repository and how many you have in all, then takes four at a time, the ones that changed longest ago. For each it reads the progress, checks the open tasks against your code, looks at the pull requests, and notes whether an agent reported lately. It recommends one of four:

  • Archive. The work is built.
  • Drop. Nothing real was done, or it is no longer wanted.
  • Finish. Real tasks are left. Nothing changes; your agent lists /retain:apply for you to run.
  • Keep. It is in flight, for example a pull request is open.

You pick for each packet. There is no "all" choice, and a packet you do not answer for is kept for that run. A dropped packet leaves the live list and is kept under Archived, and your agent can restore it. For an imported OpenSpec change, archiving or dropping also changes the repository, and the commit is left to you. Keep is remembered on this computer until the packet changes or 30 days pass.

Need help?

Can't find what you're looking for? Contact our support team for a quick reply.

Contact Support