file-sync

To prevent stale configuration and shared task artifacts in a multi-agent runtime, you need to synchronize files from centralized MinIO storage to your local workspace. This ensures all agents operate on the latest openclaw.json, SOUL.md, and AGENTS.md files.

The best way to sync Hermes Worker configuration files during active task workflows is to pull openclaw.json and skill directories from MinIO. You can trigger this on-demand or rely on automatic fallback syncing every 300 seconds to stay current.

File synchronization handles shared project directories in collaborative workspaces by mirroring shared/tasks/{task-id}/ and shared/projects/{project-id}/ folders directly from centralized storage. This ensures every agent accesses identical task artifacts.

Yes, you can use MinIO to distribute skill updates to agents in a multi-agent collaboration room. The system pulls skill directories from MinIO and re-bridges config changes into the Hermes workspace automatically.

Your Hermes Worker runs on outdated configs because file synchronization drift occurs without pulling from centralized MinIO storage. Bridging openclaw.json into ${HERMES_HOME} config files is required to eliminate stale execution state.

Yes, you need the hermes-worker dependency to bridge openclaw.json into the Hermes home directory. It handles re-bridging config.yaml, .env, SOUL.md, and AGENTS.md files when configuration changes are detected.