Cairn
NousResearch/hermes-agent

Fix reply_to metadata forwarding in gateway/qqbot

Cluster 44294 · 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 changes address how reply_to information is extracted from gateway metadata and forwarded through to adapter parameters, including during background task completion delivery. All three items relate to preserving reply context across the gateway and qqbot layers.

Open issues1

  • Issue#44294fix(qqbot): bridge reply_to from gateway metadata to adapter parameter

Open PRs2

  • PR#44307fix(qqbot): extract reply_to from gateway metadata before discarding
  • PR#134416fix(gateway): forward event_message_id as reply_to in background task completion delivery
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/44294.json
cluster/44294.md