# NousResearch/hermes-agent · Discord reply/forward context lost before agent turn

## Open now

- 1 issue, 0 PRs open on GitHub.
- #119230: \[Bug\]: Discord reply/forward context is lost before the agent turn

A 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.

## TL;DR

- 4 member(s): 1 open issue(s), 0 closed issue(s), 0 open PR(s), 0 merged PR(s), 3 PR(s) closed without merging.
- No fix has been merged to main; one or more PRs were attempted (see below).
- **Recommended:** review the prior/competing PR(s) below. A fix was attempted but not merged; your case may extend or revive that work.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `unresolved`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.50`: the share of member 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.

## Open related issues

- #119230: \[Bug\]: Discord reply/forward context is lost before the agent turn

## Prior & competing PRs

- **#119234: fix(gateway): preserve Discord reply and forward context**. closed without merge
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `#119230`, `#119312`, `#119234`
- **#119257: fix(discord): retain reply/forward context for the agent turn**. closed without merge
  - maintainer direction: category `silent_close`; implication `active`
- **#119312: fix(gateway): retain Discord reply/forward context metadata before agent turn**. closed without merge
  - maintainer direction: category `silent_close`; implication `active`

## Fix status

- No merged fix on record.
- Subsystem: `gateway`