Recovery

Coterie preserves durable tasks, messages, transcripts, and workspaces when the foreground exits, a worker fails, or a run stops. Recovery starts from the recorded state; it does not assume that an uncertain process has exited or that uncommitted work can be discarded.

Return to an active run

Run coterie again from the primary project. Coterie reconnects to an active supervisor or conservatively restarts an indexed run after a crash. The fresh foreground Codex session gets its current context from durable state. It does not reattach the old TUI session.

Inspect the run when its state is unclear:

coterie status
coterie doctor
coterie events

Continue a stopped run

Stopping a run retains its work. Select the original run before launching a new foreground session:

coterie run list
coterie run recover <run-id> --reason "Continue retained work."
coterie

Recovery verifies saved configuration, project identity and leases, process exits, and workspace ownership. If a replacement run exists, stop it first. Changed policy must be restored. Retrying an uncertain recovery uses the same operation ID and identical arguments; see JSON and retry rules.

Continue an interrupted worker task

If a Git worktree worker exited before submission, inspect its assignment and transcript. Once doctor and the recorded session state establish that it has exited, recover the assignment:

coterie task recover --assignment <assignment-id> --reason "Worker exited before submission."
coterie spawn worker --task <reopened-task-id>

The original worktree, files, index, commits, transcript, and reference remain preserved. The continuation receives a fresh worktree and a handoff link. Use coterie assignment show <source-assignment-id> --json to read the recorded Git snapshot and any sourced validation report. Transfer useful changes deliberately, validate them in the new workspace, and follow the normal commit, submission, integration, and closure steps.

An optional --report <JSON> can record validation evidence and unfinished steps, each with a source reference. An absent report means the evidence is unknown. The handoff notes on GitHub show the full format.

An already submitted task follows normal review and integration. An authorized coordinator uses task resubmit to correct an unintegrated Git submission. Recovery never silently grants write access to preserved source work.