Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix Feature: include Telegram forum topic names in dashboard session labels [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#68652•Fetched 2026-04-19 15:09:05
View on GitHub
Comments
0
Participants
1
Timeline
0
Reactions
0
Author
jamiezigelbaumjamiezigelbaum
Participants
jamiezigelbaumjamiezigelbaum

When OpenClaw mirrors Telegram forum-topic chats into the dashboard / Control UI session picker, please include the human Telegram topic name in the stock session label.

Root Cause

OpenClaw already creates separate sessions for Telegram forum topics, which is good. But in the session picker, those sessions are still hard to distinguish when the label only shows the group name or a generic slug.

In a real setup with multiple active Telegram topics under one group, the dashboard becomes much harder to use because the operator cannot immediately tell which session corresponds to which Telegram topic.

RAW_BUFFERClick to expand / collapse

Summary

When OpenClaw mirrors Telegram forum-topic chats into the dashboard / Control UI session picker, please include the human Telegram topic name in the stock session label.

Why this matters

OpenClaw already creates separate sessions for Telegram forum topics, which is good. But in the session picker, those sessions are still hard to distinguish when the label only shows the group name or a generic slug.

In a real setup with multiple active Telegram topics under one group, the dashboard becomes much harder to use because the operator cannot immediately tell which session corresponds to which Telegram topic.

Current behavior

Telegram forum topics get isolated session keys, but the visible dashboard label does not include the topic title.

Example of current stored metadata from a live setup on OpenClaw 2026.4.15:

  • session key: agent:main:telegram:group:-1003945702288:topic:1
  • displayName: telegram:g-olympus
  • subject: Olympus
  • origin.label: Olympus id:-1003945702288 topic:1

So the topic id is preserved, but the human topic title is not surfaced in the session picker.

Expected behavior

If OpenClaw knows the Telegram forum topic name, the stock dashboard session label should include it automatically.

Examples:

  • telegram:g-olympus / treasury-working-group
  • Olympus · Treasury Working Group
  • any similar stock format that makes topics easy to distinguish at a glance

The important part is that this should be built into normal session metadata / UI labeling, not require any periodic relabeling helper or external sync script.

Why this seems like a natural stock feature

OpenClaw already documents that:

  • Telegram forum topics have separate session keys
  • session entries can carry labeling metadata like displayName, subject, and origin.label
  • recent releases already learned human Telegram topic names for agent context and persisted them

That suggests the remaining gap is mainly surfacing the already-known topic title in stock session labeling.

Reproduction

  1. Enable Telegram forum-group access in OpenClaw
  2. Use multiple topics inside the same Telegram forum group
  3. Send messages so each topic gets its own OpenClaw session
  4. Open the Control UI / dashboard session picker
  5. Observe that the sessions are distinct, but the visible names do not clearly include the human topic title

Request

Please make stock OpenClaw include Telegram forum topic titles in session labels shown in the dashboard / Control UI when those titles are known, without requiring any external relabeling machinery.

If helpful, I would expect this to reuse the existing built-in session metadata path rather than introducing a separate background sync mechanism.

extent analysis

TL;DR

Update the session label generation to include the Telegram forum topic title, utilizing existing metadata like subject or origin.label.

Guidance

  • Review the current implementation of session label generation to identify where the displayName is constructed and how it can be modified to include the topic title.
  • Consider reusing the subject field, which already contains the human-readable topic name, to update the displayName or introduce a new field that combines the group name with the topic title.
  • Investigate how the origin.label is populated and whether it can be leveraged to automatically include the topic title in the session label.
  • Evaluate the feasibility of introducing a new formatting option for session labels that allows for the inclusion of the topic title, ensuring consistency across different Telegram forum groups and topics.

Example

// Pseudocode example of updating the displayName
function generateSessionLabel(sessionMetadata) {
  const groupName = sessionMetadata.groupName;
  const topicTitle = sessionMetadata.subject; // or origin.label
  return `telegram:${groupName} / ${topicTitle}`;
}

Notes

The solution may require adjustments to the existing session metadata structure or the introduction of a new field to accommodate the topic title. Additionally, ensuring consistency in formatting and handling cases where the topic title is not available or changes over time will be essential.

Recommendation

Apply a workaround by modifying the session label generation to include the Telegram forum topic title, as this seems to be a natural extension of the existing functionality and does not require introducing separate background sync mechanisms.

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…

FAQ

Expected behavior

If OpenClaw knows the Telegram forum topic name, the stock dashboard session label should include it automatically.

Examples:

  • telegram:g-olympus / treasury-working-group
  • Olympus · Treasury Working Group
  • any similar stock format that makes topics easy to distinguish at a glance

The important part is that this should be built into normal session metadata / UI labeling, not require any periodic relabeling helper or external sync script.

#device allocation#model download#tokenizer error#prompt formatting#chain 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