NousResearch/hermes-agent

Agent message persistence and stall recovery work

Cluster 45110 · agent. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

0open issues
0open PRs
4items grouped
Known?
Yes. 4 related items grouped here, 1 issue already closed.
Fix event
No fix has been merged to main. 3 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
Nothing open on GitHub.

These items address a scenario where user prompts are lost when a turn's first response never completes, with fixes focused on persisting inbound messages to the state database early and handling stale or incomplete turns.

Open issues0

No open issues.

Open PRs0

No open pull requests.

3 PRs closed without merging

From the close comments: done elsewhere 2 · superseded by another PR 1

  • #45887 fix(agent): harden early-turn persistence to survive session-DB failures (#45110) · done elsewhere → #45110
  • #52907 fix(agent): persist inbound user message to state.db on receipt (#45110) · superseded by another PR
  • #52985 fix(agent): persist user message on receipt + retry/discard stale turns (#45110) · done elsewhere → #2, #45110
Closed issues · 1
  • Closed#45110Prompt is lost entirely when a turn's first response never completes (stall or client disconnect)
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.50: 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
Closed issues
1
Attempts
3 PRs closed without merging

For your agent

The same facts, typed.