openclaw - 💡(How to fix) Fix [Feature]: Show display name instead of user ID in session list

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Fix Action

Fix / Workaround

Frequency: Always

  • Every session created by a channel peer uses the raw peer ID as the session label
  • No workaround exists without custom scripting or third-party tools

Consequence:

  • Slower triage when switching between user sessions
  • Higher cognitive load managing multiple simultaneous users
  • Operators resort to keeping notes/records of "which ID = which user" externally — a manual workaround
RAW_BUFFERClick to expand / collapse

Summary

Feature Request: Show display name instead of user ID in session list

What problem does this solve? When managing multiple Feishu (or other channel) users, the session list shows ou_7f1ab2cd5fd91a2899c407e52bd75c18 instead of the user's actual name like "张三". The same applies to Discord (shows user IDs), Telegram, WhatsApp, etc.

This makes session management confusing and slow, especially when helping multiple users.

Where is this visible?

  1. Control UI session sidebar — shows truncated ou_7f1ab2… instead of contact name
  2. openclaw status → Sessions table — shows full ou_7f1ab2cd5fd91a2899c407e52bd75c18
  3. sessions_list ACP tool output — same

Proposed solution: Add a configurable sessionLabelFormat option (or similar) that lets the gateway resolve channel peer IDs to display names in session listings.

For Feishu specifically, channels.feishu.resolveSenderNames: true already exists for inbound message resolution — a similar mechanism could be used to resolve sender names into session labels for display purposes.

Suggested implementation:

  • Add a config option like channels.<channel>.sessionLabelFormat: "{displayName}" that falls back to "{peerId}" if name resolution fails
  • Or, auto-resolve sender names for session list display when resolveSenderNames: true
  • This would benefit all channels that support it (Feishu, Discord, Telegram, etc.)

Alternatives considered:

  • Manual label override per session key — too cumbersome
  • OpenClaw Studio — external tool, not core product

Additional context: OpenClaw already stores sender names in transcript metadata. The capability exists; the display layer just doesn't use it for session labels.

Problem to solve

When managing multiple Feishu (or other channel) users, the session list shows ou_7f1ab2cd5fd91a2899c407e52bd75c18 instead of the user's actual name like "张三". The same applies to Discord (shows user IDs), Telegram, WhatsApp, etc.

Proposed solution

Add a configurable sessionLabelFormat option (or similar) that lets the gateway resolve channel peer IDs to display names in session listings.

For Feishu specifically, channels.feishu.resolveSenderNames: true already exists for inbound message resolution — a similar mechanism could be used to resolve sender names into session labels for display purposes.

Alternatives considered

  • Manual label override per session key — too cumbersome
  • OpenClaw Studio — external tool, not core product

Impact

Affected users/systems/channels:

  • All OpenClaw operators running multi-user Feishu, Discord, Telegram, WhatsApp, or similar channel integrations
  • Particularly felt when the operator manages 5+ users — session list becomes a wall of opaque ou_/uc_/dg_ prefixes

Severity: Annoying / friction-increasing

  • Doesn't block workflows entirely, but slows down session lookup significantly
  • Forces the operator to hover/expand every truncated key to identify the user
  • In Control UI sidebar, the truncated session keys are nearly unreadable

Frequency: Always

  • Every session created by a channel peer uses the raw peer ID as the session label
  • No workaround exists without custom scripting or third-party tools

Consequence:

  • Slower triage when switching between user sessions
  • Higher cognitive load managing multiple simultaneous users
  • Operators resort to keeping notes/records of "which ID = which user" externally — a manual workaround

### Evidence/examples

_No response_

### Additional information

OpenClaw already stores sender names in transcript metadata. The capability exists; the display layer just doesn't use it for session labels.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix [Feature]: Show display name instead of user ID in session list