Summary

Telegram setMyCommands fails on gateway startup because dock native commands use hyphens (dock-telegram) which are invalid — Telegram only allows lowercase, digits, and underscores.

Steps to reproduce

1. Configure a Telegram bot
2. Start the gateway
3. Observe error in logs

Expected behavior

Commands register successfully, no errors.

Actual behavior

[telegram] telegram setMyCommands failed: GrammyError: Call to 'setMyCommands' failed! (400: Bad Request: BOT_COMMAND_INVALID)

Environment

• Clawdbot version: 2026.1.14
• OS: macOS
• Install method: pnpm

Logs or screenshots

10:25:20 [telegram] [default] starting provider (@jlibert_clawd_bot)
10:25:20 [telegram] telegram setMyCommands failed: GrammyError: Call to 'setMyCommands' failed! (400: Bad Request: BOT_COMMAND_INVALID)

Prompt

The gateway logs telegram setMyCommands failed: BOT_COMMAND_INVALID. Find the native command registration for dock commands and fix the invalid character (hyphen) to comply with Telegram's command format.

Expected fix: src/auto-reply/commands-registry.data.ts:251 — change dock-${dock.id} → dock_${dock.id} for nativeName. Text alias /dock-telegram unchanged.

I know you don't like PR anymore Peter so here ya go.