Summary

Implements plugin support for Telegram-specific features:

1. sendPayload handler - Enables channel-specific data via the channelData pattern (inline buttons, etc.)
2. Plugin command menu sync - Merges plugin commands into Telegram's / autocomplete menu
3. Plugin command handlers - Registers bot.command() handlers so plugin commands execute deterministically
4. Button extraction in deliverReplies - Extracts and sends buttons from plugin responses
5. Gateway method types - Exports gateway request handler types for plugin authors

Motivation

Plugins need access to Telegram-specific features and gateway RPC methods:

• Inline buttons: Plugins want button-driven workflows without custom ReplyPayload types
• Command discovery: Plugin commands registered internally don't appear in Telegram's menu
• Command execution: Plugin commands must execute deterministically, not fall through to LLM
• Button delivery: Plugin command responses with buttons need proper rendering
• Gateway methods: Plugins want to expose RPC-style methods for programmatic access

The infrastructure exists in core but wasn't fully wired up for plugins.

Changes

1. Telegram sendPayload Handler

• Add sendPayload handler to telegramOutbound adapter
• Extract telegram.buttons from payload.channelData
• Pass buttons to existing sendMessageTelegram function (already supports this)

2. Plugin Command Menu Sync

• Import getPluginCommandSpecs() in bot-native-commands.ts
• Merge plugin commands into allCommands array
• Commands appear in Telegram's / menu alongside native commands

3. Plugin Command Handler Registration

• Register bot.command() handlers for each plugin command
• Match and execute plugin commands via executePluginCommand()
• Apply full authorization checks (same as native commands)
• Deliver results through existing Telegram delivery pipeline

Critical Fix: Without this, plugin commands show in the menu but fall through to the general message handler, where the LLM processes them conversationally instead of executing them deterministically.

4. Button Extraction in deliverReplies

• Extract buttons from reply.channelData?.telegram?.buttons in deliverReplies()
• Build inline keyboard markup using buildInlineKeyboard()
• Pass reply_markup to sendMessage() API
• Buttons are attached to the first chunk when text is chunked

Critical Fix: Plugin commands can return buttons in channelData, but deliverReplies() was ignoring them. Now buttons render properly.

5. Gateway Method Types Export

• Export GatewayRequestHandler, GatewayRequestHandlerOptions, RespondFn in plugin-sdk
• Enables plugins to register gateway methods with proper types

Example Usage

Inline Buttons

return {
  text: "Choose an option",
  channelData: {
    telegram: {
      buttons: [
        [{ text: "Option A", callback_data: "/command option-a" }],
        [{ text: "Option B", callback_data: "/command option-b" }]
      ]
    }
  }
};

Gateway Methods

api.registerGatewayMethod("my-plugin.action", async ({ params, respond }) => {
  try {
    const result = await doSomething(params);
    respond(true, { result });
  } catch (error) {
    respond(false, { error: error.message });
  }
});

Testing

• Builds successfully
• Follows existing patterns (sendText/sendMedia, voice-call plugin)
• skill-flow plugin: 46/46 tests pass, 0 lint errors
• Buttons render correctly in Telegram

Use Case

Enables the skill-flow plugin to:

• Send button-driven workflows in Telegram
• Show commands in Telegram's autocomplete menu
• Execute commands deterministically (not via LLM interpretation)
• Render inline keyboard buttons in responses
• Expose gateway methods for programmatic flow creation

🤖 AI-Assisted: Generated with Claude Sonnet 4.5