Cairn
NousResearch/hermes-agent

Signal group message routing bugs and fixes

Cluster 30309 · gateway. Data as of

3 open items. Fix attempted, not merged.

The short answer

1open issue
2open PRs
4items grouped
Known?
Yes. 4 related items grouped here, 1 issue 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 issues and pull requests concern Signal group messages failing due to missing group ID patterns in target parsing and absent Signal entries in authorization mappings. Multiple fixes were proposed or applied to address these routing gaps.

Open issues1

  • Issue#58175Signal group messages rejected by _is_user_authorized despite passing adapter-level filter

Open PRs2

  • PR#58187fix(gateway): add Signal to platform_group_user_env_map for group message auth
  • PR#97164fix(signal): preserve unmentioned group context for persona triggers
Closed issues · 1
  • Closed#30309[Setup]: Signal → Group ID does not work
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.39: 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
0 PRs closed without merging

For your agent

The same facts, typed.

cluster/30309.json
cluster/30309.md