convention-sync

Syncing local cursor configuration uses content-hash comparisons to mirror files to a remote repository, blocking operations when local environments are stale to prevent data loss and ensure cross-machine consistency.

Configuration drift happens when local environment files diverge from a shared repository, causing shared Claude memories and hook registrations to function inconsistently across different machines and breaking orchestration projection.

Yes, syncing your local cursor setup requires gh CLI and jq to execute version control operations and perform JSON-based state validation, alongside git and rsync for managing bidirectional file transfers.

Yes, you can dry-run the configuration sync to check the current status of your local cursor setup against the repository, reviewing file differences before executing any bidirectional transfers or overwrites.

Content hashing prevents stale configuration overwrites by comparing file states between the local environment and remote repository, blocking sync operations when local files are outdated to ensure cross-machine safety and data integrity.

The best way to manage shared Claude memories across machines is through orchestration projection, which automatically manages hook registrations to ensure agent-watcher systems function identically on every machine via canonical syncing.