How-To Guide
Share Memories Across Multiple Hermes Instances
Sync memory, skills, and config across multiple Hermes Agent installations using backup, import, and sync tools.
Quick answer
Share memory across Hermes instances using the backup and import commands: export the ~/.hermes memory from one machine and import it on another so a laptop, NAS, and VPS don't each learn in isolation. For true real-time sharing across agents, a shared-memory layer is the heavier alternative.
Running Hermes on multiple machines — your laptop, a NAS, a desktop, a VPS — creates a memory fragmentation problem. Each instance learns independently but doesn't share that knowledge. The backup and import commands solve this by letting you transfer complete agent state between machines.
Managed cloud · API costs included · Skill library · Cancel anytime
Before you start:
- ☑Hermes Agent installed on multiple machines
- ☑SSH or file transfer capability between machines
- ☑Same Hermes version on all machines recommended
Steps
- 1
Use hermes backup
Run 'hermes backup' on your source machine to create a backup_DATETIME.zip file
- 2
Transfer the backup
Use rsync, syncthing, or manual copy to move the backup file to your target machine
- 3
Import on target
Run 'hermes import backup_DATETIME.zip' on the target machine to restore memory and skills
- 4
Set up continuous sync (optional)
Configure syncthing or rsync cron to keep ~/.hermes/ in sync across machines
Pro Tips
- 💡Use 'hermes backup' with a --note flag to tag backups with descriptive names
- 💡Syncthing provides a GUI-based approach if you're not comfortable with rsync
- 💡Run backup before any import to preserve the target machine's current state
Troubleshooting
❌ Import fails with version mismatch
✅ Update both Hermes installations to the same version before backup/import. Run 'hermes update' on both machines.
❌ Importing over existing setup causes duplicates
✅ The import command is designed for fresh installs or explicit overwrites. Consider merging manually or starting fresh on the target.
❌ Continuous sync causes conflicts
✅ Don't run Hermes on two machines simultaneously while syncing ~/.hermes/. Stop Hermes on one machine before syncing to avoid file lock conflicts.
FAQ
Why does memory fragment across machines?
Each Hermes instance learns into its own ~/.hermes store. A laptop, NAS, and VPS accumulate separate knowledge unless you deliberately sync it.
How do I sync memory between instances?
Use the backup/export and import commands to move the memory store between machines. Schedule it if you want instances to stay roughly in step.
Is there real-time cross-instance memory?
Backup/import is point-in-time. For live sharing across agents, use a dedicated shared-memory layer — heavier, but it avoids manual syncing.