Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix Feature Request: Support custom display names for sessions [1 participants]

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…
GitHub stats
openclaw/openclaw#63204•Fetched 2026-04-09 07:57:02
View on GitHub
Comments
0
Participants
1
Timeline
1
Reactions
0
Author
eno0000eno0000
Participants
eno0000eno0000
Timeline (top)
labeled ×1

Feature Request: Support custom display names for sessions

Root Cause

Feature Request: Support custom display names for sessions

Fix Action

Workaround

Currently users can modify the session key in sessions.json, but this does not change the UI display name.

RAW_BUFFERClick to expand / collapse

Summary

Feature Request: Support custom display names for sessions

Problem to solve

Feature Description

Currently, session display names in the Control UI are auto-generated based on channel type, agent ID, and user ID (e.g., "telegram:g-agent-main-telegram-slash-xxxxxxxx").

Problem / Use Case

Users may want to rename sessions to more recognizable names for easier management, especially when managing multiple Telegram bots or sessions.

Proposed Solution

Allow users to set custom display names/labels for sessions via:

  1. sessions.json configuration
  2. CLI command (e.g., openclaw sessions rename)
  3. Control UI inline editing

Workaround

Currently users can modify the session key in sessions.json, but this does not change the UI display name.

Additional Context

  • OpenClaw version: 2026.4.8
  • Platform: Linux
  • Channel: Telegram

Proposed solution

Workaround

Currently users can modify the session key in sessions.json, but this does not change the UI display name.

Alternatives considered

No response

Impact

頻道

Evidence/examples

No response

Additional information

No response

extent analysis

TL;DR

To support custom display names for sessions, modify the sessions.json configuration or implement a custom solution using the proposed CLI command or Control UI inline editing.

Guidance

  • Modify the sessions.json configuration to update the session key, which may partially address the issue, but note that this does not change the UI display name.
  • Consider implementing a custom solution using the proposed CLI command (e.g., openclaw sessions rename) to update session display names.
  • Explore adding inline editing functionality to the Control UI to allow users to set custom display names/labels for sessions.
  • Review the OpenClaw version (2026.4.8) and platform (Linux) to ensure any custom solutions are compatible.

Example

No explicit code example is provided, but users can explore modifying the sessions.json configuration as a starting point.

Notes

The proposed solution and workaround are specific to the OpenClaw version (2026.4.8) and platform (Linux), and may not be applicable to other versions or platforms.

Recommendation

Apply workaround: Modify the sessions.json configuration as a temporary solution until a more comprehensive fix is implemented, allowing users to partially address the issue.

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…
#parallel task#integration issue#index setup#retrieval issue#search optimization

Still need to ship something?

×6

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

Back to top recommendations

TRENDING