hermes - 💡(How to fix) Fix Feature Request: Cloud Sync for All Hermes Configurations Across Devices [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
NousResearch/hermes-agent#20510Fetched 2026-05-07 03:57:40
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
2
Participants
Timeline (top)
labeled ×3
RAW_BUFFERClick to expand / collapse

Feature Request: Cloud / Cross-Device Sync for Hermes Configuration

Problem

Currently, Hermes stores all configurations, profiles, skills, sessions, and memory locally under ~/.hermes/. There is no built-in way to sync these across multiple devices (PC, laptop, etc.).

Users who work on multiple machines (e.g., desktop at home + laptop at work) have to manually export/import profiles, copy skills folders, and replicate setup on each device.

Desired Behavior

A built-in cloud sync feature that automatically synchronizes all Hermes data across devices, including:

  • Configconfig.yaml, .env (with encrypted secrets)
  • Profiles — all profile directories
  • Skills — both hub-installed and user-created local skills
  • Memory — memory store (cross-session memory/user profile)
  • Sessions — session history (optional toggle)
  • Credential Poolsauth.json

Suggested Implementation Ideas

  1. Cloud Storage Provider Backend — Let users configure a sync provider (Google Drive, Dropbox, Nextcloud, S3-compatible, or Git-based) and Hermes auto-syncs on start/stop or on schedule.

  2. Built-in Hermes Cloud Service — Optional official sync server (self-hostable?) where users log in once and all their Hermes instances stay in sync.

  3. Git-based Sync — Under the hood, use git to version and sync ~/.hermes/ to a private repo. Conflicts could be auto-merged for non-conflicting files.

  4. Encrypted Secrets.env and auth.json should be encrypted before syncing so API keys are never exposed to the sync provider.

Use Case Example

  • User sets up Hermes on PC at home with custom skills, config, and memory.
  • User goes to laptop at work, installs Hermes, logs in → everything syncs automatically.
  • Any changes made on one device (new skill, config tweak, session) propagate to all other devices.

Benefits

  • No more manual backup/restore workflows
  • Seamless multi-device Hermes usage
  • Skills and memory stay consistent across environments

Thanks for considering this! 🙏

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

hermes - 💡(How to fix) Fix Feature Request: Cloud Sync for All Hermes Configurations Across Devices [1 participants]