Description

On OpenClaw 2026.4.14 (macOS, LaunchAgent, grammY long-polling), commands.native: "auto" (default) and commands.native: true (explicit) both fail to register native Telegram bot commands via setMyCommands at gateway startup.

Steps to Reproduce

1. Fresh OpenClaw 2026.4.14 install with Telegram channel configured
2. Start gateway via LaunchAgent
3. Check logs for setMyCommands — zero attempts logged
4. Type / in Telegram DM with the bot — no autocomplete menu appears
5. Explicitly set channels.telegram.commands.native: true in openclaw.json
6. Restart gateway
7. Still no setMyCommands attempts in logs

Expected Behavior

Gateway should call setMyCommands on Telegram provider startup, registering built-in commands (help, status, new, reset, model, etc.) and user-invocable skill commands when nativeSkills is enabled.

Actual Behavior

No setMyCommands call is ever attempted. No error, no warning, no log entry about command registration at all. The code path in bot-BwMz6R6-.js that calls bot.api.setMyCommands(retryCommands) is never reached.

Workaround

Manually register commands via the Telegram Bot API:

curl -X POST "https://api.telegram.org/bot<TOKEN>/setMyCommands" \
  -H "Content-Type: application/json" \
  -d '{"commands": [{"command": "help", "description": "Show available commands"}, ...]}'

Environment

• OpenClaw: 2026.4.14 (323493f)
• Node: v25.9.0
• macOS: Darwin 25.4.0 (arm64)
• Telegram: grammY long-polling mode
• LaunchAgent: ai.openclaw.gateway

Relevant Config

{
  "channels": {
    "telegram": {
      "commands": {
        "native": true,
        "nativeSkills": true
      }
    }
  }
}

Notes

• The registration code exists in dist/bot-BwMz6R6-.js (lines referencing setMyCommands, retryCommands, BOT_COMMANDS_TOO_MUCH)
• The Telegram provider starts successfully and handles messages fine
• lossless-claw context engine errors were present during some restarts but were resolved — command registration still did not occur after clean restarts with no LCM errors