Safety, conflicts, and recovery

Bulk-deletion guard

A capture that would delete most of a project is held on the machine where it occurred. Restore the files to resume normally, or explicitly publish the deletion:

c3sync sync --confirm-deletions

Inspect conflicts

c3sync conflicts list
c3sync conflicts resolve path/to/file

Resolve the working copy manually before clearing the conflict record. Conflict sidecars are deliberately not synchronized onward as normal project files.

Time travel

c3sync checkout --list
c3sync checkout <turn>

Checkout rewinds the working tree to a captured agent turn and prints an undo command. Restore points generally follow git's object-pruning horizon, commonly around two weeks.

Git divergence

Machine-switch git friction (committed on one machine, stale HEAD on another) is handled automatically by commit-aware auto-pull; c3sync reconcile runs the same pass on demand and c3sync status reports each project's git position. Auto-pull only ever fast-forwards — a genuinely diverged repo is reported, never merged for you.

Lost hub

Back up the hub trust anchor after initialization:

c3sync hub backup --out /offline/c3sync-hub-backup.sealed

The sealed backup is required to restore the trust chain if the hub-init device is lost.