Share Memories Across Multiple Hermes Instances
Sync memory, skills, and config across multiple Hermes Agent installations using backup, import, and sync tools.
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 · 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.