pickup

To resume unfinished work from GitHub handover tasks, you can start an interactive flow to identify ready tasks, load their associated handover documents into your context, and claim them to begin working immediately.

Yes, you can claim a specific GitHub issue directly by providing its number, which skips the interactive selection process and immediately transitions the task status to in-progress for autonomous or human-in-the-loop work.

The human-in-the-loop workflow handles task state transitions through a central atomic status flip, ensuring consistent task state across sessions by safely moving tasks to in-progress and enforcing a safe close workflow upon completion.

Yes, you need vault and GitHub configuration resolution before picking up handover tasks, as the workflow enforces these settings along with owner-label rules to maintain proper task ownership and documentation access.

Human-in-the-loop processing requires interactive user input to identify and claim handover tasks, while autonomous AFK processing executes the status transition and task loading without continuous human interaction, maintaining a clear separation between the two modes.

The best way to manage handover documents when resuming scattered work sessions is to use a central status transition system that locates ready handover tasks on GitHub and automatically loads the corresponding documentation into your working context.