Summary

In Telegram forum group chats, the assistant cannot reliably resolve a topic by human-readable name (e.g. "AI безопасность") to its topic_id for routing messages. This causes repeated misrouting or extra user clarification loops.

Environment

• OpenClaw runtime in Telegram forum groups
• Channel metadata includes current topic_id, but there is no built-in topic directory/list exposed to the agent tooling context.

Reproduction

1. Use a Telegram forum group with multiple topics.
2. Ask the assistant to send/update something into another topic by name (not by numeric id), e.g. "Отправь в ветку AI безопасность".
3. Assistant cannot resolve target topic deterministically, unless a manual local mapping exists and is perfectly maintained.

Actual behavior

• Agent often needs to ask user for numeric topic id.
• If manual mapping is stale/incomplete, routing can drift (wrong topic or no send).

Expected behavior

One of the following should exist as first-class support:

1. Inject forum_topics map (topic_id <-> title) into session context for forum chats, OR
2. Add tool action to list topics in current chat (e.g. message action=topics), OR
3. Expose topic catalog via channel metadata endpoint available to agent tools.

Impact

• Frequent operational friction in daily use.
• Repeated clarification loops for the same group.
• Higher chance of misrouted messages across project topics.

Current workaround

Maintain a local manual topic map file and ask user to provide ids for new topics. Workaround is error-prone and not durable.

Priority

High (blocks reliable multi-topic operations in Telegram forum workflows).