openclaw - 💡(How to fix) Fix Telegram BOT_COMMANDS_TOO_MUCH when many skills registered [1 comments, 2 participants]

When a Clawdbot instance has many skills (60+), registering them as native Telegram bot commands via setMyCommands triggers BOT_COMMANDS_TOO_MUCH error.

• Error BOT_COMMANDS_TOO_MUCH repeats every ~90 seconds

Fix Plan

To resolve the BOT_COMMANDS_TOO_MUCH error, we will implement a solution that caps the number of commands registered to Telegram's limit.

Step-by-Step Solution:

1. Determine Telegram's Command Limit: Check the official Telegram API documentation for the maximum number of commands allowed.
2. Modify the Command Registration Code: Update the code that registers commands with Telegram to only register up to the allowed limit.
3. Implement Command Prioritization: Develop a system to prioritize which commands to register when the limit is reached.

Example Code (Python):

# Assuming a list of commands to register
commands_to_register = [...]  # list of 94 commands

# Telegram's command limit (example value)
telegram_command_limit = 50

# Prioritize commands (simple example: register the first 50 commands)
registered_commands = commands_to_register[:telegram_command_limit]

# Register the prioritized commands with Telegram
for command in registered_commands:
    # Code to register the command with Telegram
    register_command(command)

Verification

To verify the fix, restart the Clawdbot instance and check for the BOT_COMMANDS_TOO_MUCH error. The error should no longer occur, and the Telegram bot should function as expected with the limited number of registered commands.

Extra Tips

• Regularly review and update the command prioritization system to ensure the most important commands are registered.
• Consider implementing a more sophisticated command prioritization system, such as categorizing commands or allowing users to customize their registered commands.