openclaw - 💡(How to fix) Fix [Bug]: Telegram DM topic autoTopicLabel no longer renames new topics, fallback title sticks [1 participants]

Summary

Telegram DM topics are no longer getting the LLM-generated auto title reliably. The topic is created with a provisional/fallback name, then never gets renamed.

In practice, this means new Telegram threads end up keeping a title that looks like the first words of the initial prompt/request instead of the concise generated label.

Version

OpenClaw 2026.4.5

Expected

After the first user message in a new Telegram DM topic/session, OpenClaw should auto-rename the topic with the generated label from autoTopicLabel.

Actual

The new topic keeps the provisional creation-time title and never gets the follow-up rename.

Repro

1. Use Telegram DM topics.
2. Create a new thread/topic in a Telegram DM flow.
3. Send the first real message in that topic.
4. Observe that the topic keeps the fallback/provisional title instead of getting an LLM-generated one.

Notes

I checked the installed code and config locally:

• autoTopicLabel still exists and is enabled by default for Telegram DM topics.
• The rename path is still present and calls editForumTopic(...) after a generated label is returned.
• The likely failure is that the rename path is being skipped before it ever runs.

Relevant code paths in the current build:

• Auto-label generation + rename:

  • dist/bot-DYFDqLWF.js around the auto-topic-label block
  • calls generateConversationLabel(...)
  • then bot.api.editForumTopic(chatId, topicThreadId, { name: label })

• First-turn gating for that path:

  • dist/bot-DYFDqLWF.js around the isFirstTurnInSession logic
  • this checks session-store state and appears to gate auto-renaming on first-turn detection

Likely regression point

My guess is that isFirstTurnInSession is false in newly-created DM topics because the session already has prior system/bootstrap state by the time the first meaningful user turn is processed, so the auto-rename block never executes.

That would fit the observed symptom exactly:

• topic gets created with a provisional title,
• autoTopicLabel never fires,
• provisional title sticks.

Related

• Feature request: #51485
• Feature landed in: PR #51502