hermes update autostash skipping flat-install runtime state

NousResearch/hermes-agent · cluster 110648

Data as of

Nothing open on GitHub. Fix merged in #111175. Check it covers your case.

The short answer

0open issues
0open PRs
5items grouped
Known?
Yes. 5 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #111175. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #111175. That is separate from the fix event.
Still open
Nothing open on GitHub.

These issues and PRs concern a bug where the hermes update autostash mechanism sweeps live runtime files (state.db, snapshots, config) on flat installs where the checkout root equals $HERMES_HOME. The work focuses on making the autostash ignore those live runtime files.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #111175 hermes update no longer autostashes flat-install runtime state (#110648, salvage #110668)

    merged to main

    files: .gitignore, tests/hermes_cli/test_update_flat_install_state_gitignore.py

  • #111391 fix(update): flat-install runtime state (state.db, snapshots, config) no longer swept into the autostash (#110648, salvage #110668)

    merged to main

    files: .gitignore, tests/hermes_cli/test_update_flat_install_state_gitignore.py, website/docs/getting-started/updating.md

2 PRs closed without merging

From the close comments: duplicate 1 · other 1

  • #110668 fix(update): ignore flat-install runtime state so autostash cannot sweep the live state.db · other → #110670, #110668, #110648
  • #110670 fix(cli): ignore live runtime state so hermes update autostash skips it · duplicate → #110668, #110648
Closed issues · 1
  • Closed#110648[Bug]: `hermes update` sweeps the live `state.db`/`-wal` on flat installs (checkout root == $HERMES_HOME) — silent transcript loss, tracked SOUL.md can stay reverted
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.40: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means 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 Lab

At a glance

Merged PRs
#111175, #111391
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
15 Sep 2026

For your agent

The same facts, typed.