Summary

There seems to be a Telegram slash-command naming mismatch for Active Memory.

The actual command exposed in chat is:

• /active-memory

But Telegram BotFather command registration expects a normal slash command token like:

• /active_memory

Because of that mismatch, the command users can actually add in BotFather is the underscore form, while the chat-visible/runtime form is the hyphen form.

Why this is a problem

For Telegram bots, command registration is not just cosmetic. Users often rely on BotFather command lists for:

• discoverability
• tap-to-run slash commands
• onboarding and memory of available commands

Right now this creates a confusing split:

• runtime / chat uses /active-memory
• BotFather-compatible registration wants /active_memory

So the command appears "wrong" from the Telegram integration perspective.

Expected behavior

OpenClaw should expose Telegram slash commands using a BotFather-compatible command name, or provide a clear Telegram-specific alias.

For this case, likely one of these should happen:

1. expose /active_memory as the Telegram-facing slash command
2. support both /active-memory and /active_memory
3. normalize command naming per surface so Telegram gets the underscore form while other surfaces can keep the canonical hyphen form

Current observed behavior

• /active-memory is the correct runtime command in OpenClaw
• but /active_memory is the form that can actually be added directly in BotFather
• so the exposed slash-command surface and the Telegram registration surface are out of sync

Request

Could maintainers clarify the intended canonical Telegram command surface here?

This looks like a small naming bug, but it impacts command discoverability and makes Telegram slash-command setup feel broken or inconsistent.