equipe-m4-clone-local

Cloning a Hermes team from Linux to macOS requires recreating agent profiles, configs, and Slack identities on the MacBook. You must use launchctl for process orchestration and establish strict sync boundaries to separate durable knowledge from ephemeral runtime state like sessions and logs.

Bidirectional vault synchronization uses an Obsidian vault and a Git-backed configuration repo to sync durable knowledge across Linux and macOS environments. It strictly separates durable knowledge from ephemeral runtime state like SQLite databases and session logs to prevent state corruption.

Yes, you can use launchctl for Hermes agent process orchestration on macOS. A local MacBook clone of a Hermes team relies on launchctl-based process management to handle profiles and maintain operational continuity without breaking the original Linux server-side system.

Repairing Slack identity drift involves auditing and validating bot identity settings, channel configurations, and profile data across Slack and local config files. This ensures the MacBook clone maintains correct agent identities without corrupting the original server state.

Ephemeral runtime state including sessions, logs, and SQLite databases must never be synced when mirroring a Hermes team locally. Enforcing sandbox restrictions and keeping runtime state local prevents state corruption and protects the original Linux environment.

Yes, a MacBook M4 Hermes clone works with an existing Obsidian vault by using it for bidirectional knowledge synchronization alongside a Git-backed configuration repo. This setup allows active development locally while preserving knowledge sync boundaries.