Cairn
NousResearch/hermes-agent

Session ID continuity lost on cold-start eviction

Cluster 16517 · gateway. Data as of

1 open item. Fix attempted, not merged.

The short answer

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

These members address a bug where cold-starting with a known conversation slug mints a new session_id instead of reusing the existing one, breaking client-side conversation continuity after LRU eviction.

Open issues1

  • Issue#16517Bug: cold-start with conversation= mints new session_id, breaking client-side conversation continuity

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: superseded by another PR 1 · other 1

  • #16607 fix(api_server): reuse session_id for known conversation slug on cold-start (#16517) · other → #16517
  • #16635 fix(api_server): persist session_id on conversation slug to survive LRU eviction (#16517) · superseded by another PR → #16607, #16517
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.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
gateway
Closed issues
0
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/16517.json
cluster/16517.md