Cairn
NousResearch/hermes-agent

Memory sync reliability and session freeze prevention

Cluster 17403 · agent. Data as of

1 open item. Fix merged in #93455 on 24 Aug 2026. Check it covers your case.

The short answer

1open issue
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 #93455. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 0 PRs.

These items address stability issues in memory and hindsight subsystems, including session freezes caused by daemon failures or LLM errors, thread management problems under error conditions, and proposals for timeouts or circuit breakers to improve resilience.

Open issues1

  • Issue#35218[Feature]: Add 3-second degradation timeout for external memory providers (fallback to builtin when hindsight is down)

Open PRs0

No open pull requests.

Fixes on record

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

  • #93455 fix(classifier): 429 quota walls route to billing across providers; reset signals stay retryable (consolidates #39441, #63021, #74785)

    merged to main

    files: agent/error_classifier.py, tests/agent/test_error_classifier.py

2 PRs closed without merging

From the close comments: stale or abandoned 1 · superseded by another PR 1

  • #17416 fix(hindsight): add circuit breaker to prevent session freeze on daemon failure · stale or abandoned
  • #74785 fix: classify hard quota 429s as billing + prevent writer thread leak under 429 storms · superseded by another PR → 0c3a507, #93455
Closed issues · 1
  • Closed#17403Hindsight tool calls freeze session when internal LLM errors out
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.34: 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

Subsystem
agent
Merged PRs
#93455
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
24 Aug 2026

For your agent

The same facts, typed.

cluster/17403.json
cluster/17403.md