Fix hardcoded backup path in recovery guidance
Cluster 104250 · agent. Data as of
1 open item. Fix merged in #104959 on 7 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #104959. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #104959. That is separate from the fix event. - Still open
- 0 issues and 1 PR.
These items address a bug where state.db corruption recovery messages hardcoded a default backup directory path instead of interpolating the actual configured home or profile directory. The fixes ensure recovery guidance points users to their real backup location.
Open issues0
Open PRs1
- PR#104319fix(agent): interpolate the live backups dir into corruption recovery guidance
Fixes on record
-
#104959 fix(recovery): custom homes and profiles point to their actual backups (#104250, salvage #104319)
files:
agent/turn_explainers.py,gateway/run_notifications.py,tests/run_agent/test_corruption_recovery_guidance.py,tests/run_agent/test_turn_completion_explainer.py
Closed issues · 1
- Closed#104250Bug: state.db recovery guidance hardcodes ~/.hermes/backups/ while the same message interpolates HERMES_HOME
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the LabAt a glance
- Subsystem
- agent
- Merged PRs
- #104959
- Closed issues
- 1
- Attempts
- 0 PRs closed without merging
- Fix link checked
- 7 Sep 2026