# NousResearch/hermes-agent · QQ passive-reply message ID missing in media/events

## Open now

- 1 issue, 2 PRs open on GitHub.
- #83085: \[qqbot\] Media replies missing passive-reply msg_id → QQ rejects as proactive message (400 主动消息失败, 无权限)
- PR #84088: fix(qqbot): preserve passive-reply anchor for media
- PR #134416: fix(gateway): forward event_message_id as reply_to in background task completion delivery

These items address cases where the passive-reply message ID (used to satisfy QQ's requirement for reactive messaging) was not being forwarded or preserved correctly for media replies and background task event delivery, causing QQ to reject messages as unauthorized proactive messages.

## TL;DR

- 3 member(s): 1 open issue(s), 0 closed issue(s), 2 open PR(s), 0 merged PR(s), 0 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.67`: 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

- #83085: \[qqbot\] Media replies missing passive-reply msg_id → QQ rejects as proactive message (400 主动消息失败, 无权限)

## Prior & competing PRs

- **#84088: fix(qqbot): preserve passive-reply anchor for media**. open
  - maintainer direction: category `uncategorized`; implication `needs_llm`
  - files: `gateway/platforms/base.py`, `gateway/run.py`, `tests/gateway/test_background_command.py`, `tests/gateway/test_tts_media_routing.py`
- **#134416: fix(gateway): forward event_message_id as reply_to in background task completion delivery**. open
  - maintainer direction: category `silent_close`; implication `active`
  - files: `gateway/platforms/qqbot/adapter.py`, `gateway/run_turn.py`, `tests/gateway/test_all_platforms_background_reply.py`, `tests/gateway/test_background_reply_anchor.py`, `tests/gateway/test_qqbot_group_expired_reply.py`

## Fix status

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