Cairn
NousResearch/hermes-agent

WhatsApp reply context not forwarded to agent

Cluster 28823 · gateway. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

0open issues
0open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 1 issue already closed.
Fix event
No fix has been merged to main. 2 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
Nothing open on GitHub.

One bug report describes WhatsApp quotedMessageId/reply context not reaching the agent, and two pull requests propose changes to forward or propagate that context. The titles share a single theme; their current status is not stated.

Open issues0

No open issues.

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: done elsewhere 2

  • #16552 fix: propagate WhatsApp reply context · done elsewhere → 11627fd
  • #28878 fix(whatsapp): forward quotedMessageId/context to agent prompt · done elsewhere → 11627fd, #28823
Closed issues · 1
  • Closed#28823[Bug]: WhatsApp: quotedMessageId/context is not forwarded to agent — reply context is lost
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
1
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/28823.json
cluster/28823.md