Context Nine/ Code Folder Sync
Documentation menu

Operations

Run routine checks, manage the daemon, change repository membership, and respond to incidents.

The background daemon is the normal writer. Read-only status and history remain available while it runs; deliberate mutating maintenance requires an explicit service handoff.

Routine checks

codefoldersync doctorValidate configuration and hub reachability.
codefoldersync statusRead cursor, outbox, and conflict state without hashing files.
codefoldersync syncPerform an intentional foreground reconciliation.
codefoldersync verify --fullRehash the complete tree and verify accepted state.
codefoldersync service statusInspect the folder-qualified daemon.
codefoldersync service logsPrint exact service log locations.

Status meanings

clean

The local cursor matches accepted hub state and no live conflict exists.

conflict

Sync completed and preserved every version, but at least one conflict remains unresolved.

offline

The hub could not be reached. Local objects and events remain queued.

inconclusive

A filesystem, object, Git, protocol, scan, or apply invariant could not be proven.

Offline and inconclusive are never convergence success.

Single writer

The daemon holds an owner-only lock for its lifetime. Mutating foreground commands fail closed while it is active. Stop the service before a manual sync, full verification, membership change, ignore change, or Git conflict resolution, then start it again afterward.

Terminal
codefoldersync service stop
codefoldersync verify --full
codefoldersync service start

Membership and ignores

Terminal
codefoldersync repository add new-repo
codefoldersync repository remove old-repo
codefoldersync repository refresh
codefoldersync ignore push
codefoldersync ignore pull

Removing membership never deletes the repository from disk. An ignore mismatch stops synchronization until an operator explicitly pushes or pulls the folder-level contract.

Incident response

  1. Stop automated writers for apply, corruption, disk, or unsafe-path failures.
  2. Leave the workspace, outbox, object stores, hub, staging, and recovery intact.
  3. Capture doctor, status, service logs, free space, and read-only Git diagnostics.
  4. Restore connectivity or storage capacity before retrying.
  5. Run normal sync, then verify --full and git fsck --full.