Issue Station
Sign In
Tools hereToolbox

hermes - 💡(How to fix) Fix hermes update does not migrate state.db pairing data [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#15733•Fetched 2026-04-26 05:25:28
View on GitHub
Comments
0
Participants
1
Timeline
4
Reactions
0
Author
bluetianxbluetianx
Participants
bluetianxbluetianx
Timeline (top)
labeled ×4

Root Cause

Root cause (from reflog) The update did a full clone rather than git pull --ff-only, discarding the pre-existing state.

RAW_BUFFERClick to expand / collapse

During a routine update, the hermes update command performed a fresh git clone instead of a proper in-place git pull. This wiped the existing state.db, losing all pairing records and other persisted state.

Environment
- hermes-agent v0.11.0 (2026.4.23)
- macOS (launchd-managed gateway)
- Feishu integration

Reproduction steps
1. Have an existing hermes-agent deployment with paired Feishu users in state.db
2. Run hermes update
3. Gateway restarts — all users must re-pair via the pairing code flow

Root cause (from reflog)
The update did a full clone rather than git pull --ff-only, discarding the pre-existing state.

Expected behavior
hermes update should preserve ~/.hermes/state.db and other user data files, only updating the hermes-agent code in place.

Reported by: BlueTian via Hermes Agent CLI

extent analysis

TL;DR

The hermes update command should be modified to perform a git pull --ff-only instead of a fresh git clone to preserve the existing state.

Guidance

  • Verify the current hermes update command behavior by checking the git commands executed during the update process.
  • Check the hermes-agent documentation for any configuration options that control the update behavior, such as an option to preserve existing state.
  • Consider adding a pre-update hook to backup the state.db file before running the hermes update command.
  • Investigate the hermes-agent version history to see if this issue has been fixed in a later version.

Example

No code snippet is provided as the issue does not imply a specific code change.

Notes

The issue seems to be specific to the hermes-agent version v0.11.0 and the hermes update command. The fix may involve modifying the update command or adding a configuration option to preserve existing state.

Recommendation

Apply a workaround by adding a pre-update hook to backup the state.db file before running the hermes update command, as the root cause is understood and a code change is not provided.

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…
#embedding generation#cache error#pipeline error#runtime error#dependency conflict

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 hermes update does not migrate state.db pairing data [1 participants]