Emoji reaction events as agent feedback signals

NousResearch/hermes-agent · cluster 13942 · gateway

Data as of

5 open items. Fix attempted, not merged.

The short answer

4open issues
1open PR
5items grouped
Known?
Yes. 5 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
4 issues and 1 PR. Broad area: open items may be separate problems.

These issues and PRs propose routing emoji reactions from Telegram and Discord into agent pipelines as implicit feedback or confirmation signals. Proposals include env-flag-gated inbound reaction handling and treating reactions as observable learning inputs.

Open issues4

  • Issue#13942[Feature]: Route Telegram message_reaction events to the agent as observable confirmation signals
  • Issue#18408Feature: Telegram emoji reaction learning — implicit feedback from message reactions
  • Issue#29026[Feature]: Discord Reaction Support in Hermes Agent
  • Issue#34660[feature] Interpret Telegram emoji reactions as agent feedback

Open PRs1

  • PR#13992feat(telegram): inbound reaction routing behind TELEGRAM_INBOUND_REACTIONS env toggle
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.21: 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.