# NousResearch/hermes-agent · Expose stable sender identity in multi-user gateways

## Open now

- 3 issues, 1 PR open on GitHub.
- #32417: \[Gateway/Telegram\] user.id is captured but not included in shared multi-user message prefix
- #35147: \[Feature\]: Expose user_id alongside user_name in single-user session context
- #46721: Feature Request: Option to include sender_id in multi-user message prefix
- PR #76516: feat(gateway): attribute every inbound sender with stable identity

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.

## TL;DR

- 7 member(s): 3 open issue(s), 1 closed issue(s), 1 open PR(s), 1 merged PR(s), 1 PR(s) closed without merging.
- A fix was merged to main in PR #69320. Verify it addresses your case.
- **Recommended:** read PR #69320 (and any competing PRs below) before filing. Confirm the merged change covers your symptom.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `unresolved`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_PARTIAL`): 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 member 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.

## Open related issues

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

## Closed / duplicate issues

- #17916: Slack shared-thread self-mention can target the wrong user when current author ID is not exposed to the agent

## Prior & competing PRs

- **#69320: fix(slack): thread-context lifecycle — cold-start, restart rehydration, mention refresh, reply-wake**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`; implication `superseded`
  - 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`
- **#18711: fix(slack): expose shared-thread author mention**. closed without merge
  - maintainer direction: category `merged_via`; implication `superseded`; refs `#69320`, `#17916`
- **#76516: feat(gateway): attribute every inbound sender with stable identity**. open
  - maintainer direction: category `partial_fix`; implication `needs_llm`; refs `97df43bfa1d2`, `#35147`, `#76516`, `#76516`, `#76516`, `#76516`, `#374151`, `#35147`, `#76516`
  - files: `cli-config.yaml.example`, `gateway/config.py`, `gateway/run.py`, `gateway/session.py`, `hermes_cli/config.py`, `tests/gateway/test_config.py`, `tests/gateway/test_image_input_routing_runtime.py`, `tests/gateway/test_shared_group_sender_prefix.py`, `tests/hermes_cli/test_set_config_value.py`, `website/docs/user-guide/configuration.md`

## Fix status

- Merged to main in PR #69320 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-07-22`.
- Subsystem: `gateway`