feat(telegram): support custom commands in config #860
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Add
customCommandsconfig option to merge user-defined commands with native Clawdbot commands in Telegram's bot menu.Problem
When Clawdbot starts, it registers native commands (like
/status,/reset,/model) viasetMyCommands, which replaces any custom commands users had previously registered.Solution
Add a
customCommandsarray to the Telegram channel config that gets merged with native commands when callingsetMyCommands.Config example:
{ "channels": { "telegram": { "customCommands": [ { "command": "backup", "description": "Git backup" }, { "command": "generate", "description": "Create an image" }, { "command": "check_email", "description": "Inbox summary" } ] } } }Behavior:
Changes
src/config/types.ts: AddTelegramCustomCommandtype andcustomCommandsfieldsrc/config/zod-schema.ts: Add schema validation for custom commandssrc/telegram/bot.ts: Merge native + custom commands insetMyCommandscall