Cairn
NousResearch/hermes-agent

Gateway DM sessions thread_id mismatch handling in /sessions

Cluster 67943 · gateway. Data as of

3 open items. Fix attempted, not merged.

The short answer

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

These items concern the gateway's handling of thread_id for direct-message sessions, where a mismatch is reported to leave the /sessions listing empty. Two members propose skipping thread_id comparison for DM sessions in the listing and in the origin and resume-target checks.

Open issues1

  • Issue#67943gateway: /sessions empty when DM sessions have mismatched thread_id

Open PRs2

  • PR#67945fix(gateway): skip thread_id comparison for DM sessions in /sessions listing
  • PR#68024fix(gateway): skip thread_id comparison for DM sessions in _same_origin_chat and _resume_target_allowed
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
0 PRs closed without merging

For your agent

The same facts, typed.

cluster/67943.json
cluster/67943.md