Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix WebChat: Add human-readable session aliases in sidebar [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#60530•Fetched 2026-04-08 02:50:00
View on GitHub
Comments
0
Participants
1
Timeline
0
Reactions
0
Author
yoonow-gdiyoonow-gdi
Participants
yoonow-gdiyoonow-gdi
  • When using WebChat alongside Telegram (forum topics), the sidebar fills with dozens of sessions — main sessions, subagent sessions, cron sessions — all with cryptic keys.
  • This makes it hard to find and switch between conversations.
  • Subagent sessions (e.g. hawk-daily-memory-v3, sentinel-morning-brief-security) are slightly better since they have labels, but the main topic-based sessions are the worst offenders.

Root Cause

  • When using WebChat alongside Telegram (forum topics), the sidebar fills with dozens of sessions — main sessions, subagent sessions, cron sessions — all with cryptic keys.
  • This makes it hard to find and switch between conversations.
  • Subagent sessions (e.g. hawk-daily-memory-v3, sentinel-morning-brief-security) are slightly better since they have labels, but the main topic-based sessions are the worst offenders.

Code Example

telegram:g-leaf · telegram:group:-1003789128818:topic:167
telegram:g-leaf · telegram:group:-1003789128818:topic:158
webchat:g-agent-main-main
RAW_BUFFERClick to expand / collapse

Problem

The WebChat sidebar displays raw session keys like:

telegram:g-leaf · telegram:group:-1003789128818:topic:167
telegram:g-leaf · telegram:group:-1003789128818:topic:158
webchat:g-agent-main-main

These are unreadable for end users. It's nearly impossible to tell which session is which without memorizing internal IDs.

Proposed Solution

Allow users to set display aliases for sessions in the WebChat sidebar. For example:

CurrentDesired
telegram:group:-1003789128818:topic:167📱 일상
telegram:group:-1003789128818:topic:158💼 업무
telegram:group:-1003789128818:topic:3⚙️ 관리
webchat:g-agent-main-main🏠 Main

Options to consider

  1. Config-based: A sessionAliases map in openclaw.json that maps session keys to display names
  2. Per-session metadata: A /label or /alias slash command to name a session
  3. Auto-derive: Use Telegram topic names or Discord channel names as default labels when available

Option 3 would cover most cases automatically without user configuration.

Context

  • When using WebChat alongside Telegram (forum topics), the sidebar fills with dozens of sessions — main sessions, subagent sessions, cron sessions — all with cryptic keys.
  • This makes it hard to find and switch between conversations.
  • Subagent sessions (e.g. hawk-daily-memory-v3, sentinel-morning-brief-security) are slightly better since they have labels, but the main topic-based sessions are the worst offenders.

extent analysis

TL;DR

Implementing a feature to allow users to set display aliases for sessions in the WebChat sidebar can improve readability and usability.

Guidance

  • Consider implementing a sessionAliases map in openclaw.json to store custom display names for sessions.
  • Evaluate the feasibility of using a /label or /alias slash command to allow users to name sessions directly.
  • Investigate auto-deriving labels from Telegram topic names or Discord channel names as a default option.
  • Assess the trade-offs between user configuration, per-session metadata, and auto-derived labels to determine the best approach.

Example

No explicit code example is provided, but a potential implementation could involve adding a sessionAliases object to the openclaw.json configuration file, like so:

{
  "sessionAliases": {
    "telegram:group:-1003789128818:topic:167": "일상",
    "telegram:group:-1003789128818:topic:158": "업무",
    "webchat:g-agent-main-main": "Main"
  }
}

Notes

The best approach will depend on the specific requirements and constraints of the WebChat application, including user experience, performance, and maintainability considerations.

Recommendation

Apply a workaround by implementing a sessionAliases map in openclaw.json to allow users to customize display names for sessions, as this provides a flexible and user-configurable solution.

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…
#vector store#embedding generation#cache error#pipeline error#runtime error

Still need to ship something?

×6

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

Back to top recommendations

TRENDING