DM and thread session context mixing fixes

NousResearch/hermes-agent · cluster 39572 · gateway

Data as of

4 open items. Fix attempted, not merged.

The short answer

2open issues
2open PRs
4items grouped
Known?
Yes. 4 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
2 issues and 2 PRs.

These issues and pull requests address bugs where DM sessions had mismatched or incorrectly compared thread IDs, causing session listing problems and context mixing between Discord threads. Fixes involve skipping thread_id comparisons for DM sessions and using effective channel references for backfill.

Open issues2

  • Issue#39572Discord thread sessions appear to mix context between threads
  • 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 (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.39: 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.