NousResearch/hermes-agent
Discord reply/forward context lost before agent turn
Cluster 119230 · gateway. Data as of
1 open item. Fix attempted, not merged.
The short answer
1open issue
0open PRs
4items grouped
- Known?
- Yes. 4 related items grouped here, 0 issues 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
- 1 issue and 0 PRs.
Next step: read the attempts below. Your case may extend or revive that work.
Pick up a Lab taskA bug was identified where Discord reply and forward context metadata is dropped before the agent turn. Multiple fixes were proposed or applied to preserve this context.
Open issues1
- Issue#119230[Bug]: Discord reply/forward context is lost before the agent turn
Open PRs0
3 PRs closed without merging
From the close comments: closed without comment 2 · done elsewhere 1
-
#119234 fix(gateway): preserve Discord reply and forward context · done elsewhere →
#119230,#119312,#119234 - #119257 fix(discord): retain reply/forward context for the agent turn · closed without comment
- #119312 fix(gateway): retain Discord reply/forward context metadata before agent turn · closed without comment
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.00means 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 LabAt a glance
- Subsystem
- gateway
- Closed issues
- 0
- Attempts
- 3 PRs closed without merging