hermes-profiles-git-sync

Agent profile synchronization across Mac and OVH is maintained through a git-backed monorepo workflow that preserves configuration integrity and prevents runtime contamination. This approach handles identity migration and multi-environment profile management safely.

Replacing shared symlinks with independent profile directories requires an emancipation workflow that moves configurations to isolated directories. This process ensures safer profile isolation and prevents runtime conflicts during synchronization.

Git and rsync are required for Hermes profile synchronization, with git providing source control backing and rsync handling skill propagation. This setup supports cron-based backup sync and validation of configuration drift.

Cron-based profile sync fails when stale Slack IDs, duplicated processes, or broken symlinks cause runtime contamination and configuration drift. Validating Slack IDs, checking config drift, and verifying launchd or cron state resolves these common failure modes.

Auditing a Hermes profile sync setup involves checking git-backed source control status, rsync skill propagation paths, and validating Slack IDs alongside launchd or cron state. This identifies config drift and prepares safe identity migration across environments.