Queue and Lifecycle

Queue is retained work state

The Queue contains Annotations available to agents and history retained from completed work. It is not a disposable clipboard and it does not remove work merely because Watch delivered it.

Lifecycle authority

Pending means an Annotation is available to Claim. Claim gives one agent temporary ownership. A Work Notice explains why an attempt could not proceed without inventing a separate blocked lifecycle state.

Resolved retains completed work; a Design Action also retains its required Resolution Record. Discarded intentionally closes work without implementation. Deletion is the separate, permanent removal action.

Read the state before taking action

Open the Queue to inspect saved feedback and its status. Pending means the work is available; Claimed means an agent has temporary ownership. Reading or watching the Queue does not Claim the work, and a Claim alone does not mean the source has changed.

When work returns to Pending with a Work Notice, read the explanation before retrying. Repair the missing prerequisite or clarify the request, then ask the agent to claim it again. If a session was interrupted, have the next agent inspect both the Annotation and the current source before continuing.

Close work or remove its history

Discard an Annotation when you no longer want its request implemented. Delete it when you want the retained record removed permanently. Neither action is a source-code undo; ask your agent separately if an implementation also needs to be reverted.

In Settings → Data & Storage, review stored projects and choose Delete project data, Delete old history when available, or Clear all Waypoint data. Read the confirmation before clicking again. When unfinished Variants are present, the confirmation explicitly includes discarding them.

Deleting stored Variant data does not clean temporary code out of your repository. If an agent created a Scaffold, arrange source cleanup before deleting the records it needs to understand that work.