Cairn

Expose stable sender identity in multi-user gateways

NousResearch/hermes-agent · cluster 17916 · gateway

Data as of

4 open items. Fix merged in #69320. Check it covers your case.

The short answer

3open issues
1open PR
7items grouped
Known?
Yes. 7 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #69320. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
3 issues and 1 PR.

These items concern capturing and surfacing user/sender IDs (not just names) in message prefixes and session context across Telegram, Slack, and other gateways. The common thread is making stable sender identity available to agents in multi-user and shared-thread scenarios.

Open issues3

  • Issue#32417[Gateway/Telegram] user.id is captured but not included in shared multi-user message prefix
  • Issue#35147[Feature]: Expose user_id alongside user_name in single-user session context
  • Issue#46721Feature Request: Option to include sender_id in multi-user message prefix

Open PRs1

  • PR#76516feat(gateway): attribute every inbound sender with stable identity

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #69320 fix(slack): thread-context lifecycle — cold-start, restart rehydration, mention refresh, reply-wake

    merged to main

    files: contributors/emails/[redacted:email], contributors/emails/[redacted:email], contributors/emails/[redacted:email], contributors/emails/[redacted:email], gateway/run.py, gateway/session.py, plugins/platforms/slack/adapter.py, tests/gateway/test_session.py, tests/gateway/test_shared_group_sender_prefix.py, tests/gateway/test_slack.py, tests/gateway/test_slack_approval_buttons.py, tests/gateway/test_slack_mention_humanization.py, tests/gateway/test_slack_wake_external_bot_messages.py

1 PR closed without merging

From the close comments: merged via another change 1

  • #18711 fix(slack): expose shared-thread author mention · merged via another change → #69320, #17916
Closed issues · 1
  • Closed#17916Slack shared-thread self-mention can target the wrong user when current author ID is not exposed to the agent
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
Merged PRs
#69320
Closed issues
1
Attempts
1 PR closed without merging
Fix link checked
22 Jul 2026

For your agent

The same facts, typed.

cluster/17916.json
cluster/17916.md