Retain / User Guide
Back to User Guide
Productivity

Closing the loop on a thread

Invalid Date
3 min read

Work that ends in a repository does not tell the Thread it was for. A Thread is the running state of one matter, with what is owed on it. Closing the loop means linking that work to its Thread, letting Retain follow it, and recording the outcome once you confirm it is done. Retain never completes anything on its own.

Link work to a Thread

Link work that is still changing on your computer: an OpenSpec change or a Markdown checklist with checkboxes.

  • With your agent. Ask it to link the change to a Thread. It lists the work in the folder and the Threads each could advance, and links after your yes. It can also name which of the Thread's owed actions the work serves.
  • On the Mac. Drop an OpenSpec change folder or a checklist onto a Thread. The file stays on your Mac.
  • Suggestions. When your agent syncs, Retain can suggest a Thread for new work in a project you already linked. It shows as "Link ... ?" under Needs your answer in the digest, and nothing is linked until you say yes.

Linked work shows in the Thread's Work section, labelled as coming from your files and not from a meeting or an email. On the Mac, choose Unlink from Thread on its row to remove the link. What it already recorded stays on the timeline.

To have Retain hold a copy of a file, for example to read it on your phone, import it as a draft instead. A work file is never saved as a note, because a note counts as something you said.

What Retain records

Retain keeps a title, a short synopsis, progress as done of total, a state and a revision. It never keeps file contents or paths.

  • Daily snapshot. At most one a day for each piece of work, and only when it changed. It appears on the timeline as "Progress on your linked work".
  • Shipped. One record, when the work finishes: an OpenSpec change is archived, or every checkbox is ticked. It appears as "Your linked work finished".

Retain reads your files when your agent syncs with /retain:sync, and when the Mac app refreshes the work you linked from it. See The morning digest.

Nothing is completed for you

A snapshot or a shipped record informs. It does not move the Thread. When linked work ships and the Thread still owes something, Retain asks "Is it done?" in three places:

  • In the digest, under Needs your answer.
  • In the Work list, as "Shipped. Mark done?". Choose Mark Done from the row's menu.
  • In /retain:sync, when you run it yourself. The scheduled morning run only lists the question.

What a confirmed outcome does

When you say yes, Retain records an outcome on the Thread as your own move. If the Thread was in Action owed, it leaves at once, tagged Provisional with the note that it moved because of what you reported. Retain then re-reads the Thread. If the evidence agrees, the new status replaces the tag. If it does not, for example another item is still owed, the Thread returns to Action owed with the reason, and your update stays on the timeline. The Still owed button on that notice puts it back yourself.

An outcome never marks a Thread Resolved. That stays your choice. When you report that someone else did something, it goes on the timeline and does not move the Thread by itself. Mark Done on a Work row records the outcome the same way and archives the item.

Say it yourself

Choose Add update at the end of a Thread's timeline on the Mac or iPhone to write what happened. It is a text note linked to that Thread, and its first save with text starts a refresh of the Thread's status. The thumbs up and thumbs down beside Archive record how the latest development turned out.

See Threads and what's owed for how status works, and The Work list for what to do with finished work.

Need help?

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

Contact Support