feat: register Telegram command menu via SetMyCommands by rfschubert · Pull Request #668 · sipeed/picoclaw

rfschubert · 2026-02-23T02:57:49Z

📝 Description

The Telegram bot does not call SetMyCommands, so users don't see the command menu when pressing / in chat. This PR registers the existing handled commands (/start, /help, /show, /list) on startup so the menu is visible.

🗣️ Type of Change

🐞 Bug fix (non-breaking change which fixes an issue)
✨ New feature (non-breaking change which adds functionality)
📖 Documentation update
⚡ Code refactoring (no functional changes, no api changes)

🤖 AI Code Generation

🤖 Fully AI-generated (100% AI, 0% Human)
🛠️ Mostly AI-generated (AI draft, Human verified/modified)
👨‍💻 Mostly Human-written (Human lead, AI assisted or none)

🔗 Related Issue

📚 Technical Context (Skip for Docs)

Reference URL: https://core.telegram.org/bots/api#setmycommands
Reasoning: telego.BotCommand and telego.SetMyCommandsParams already exist in telego v1.6.0 — no new dependencies needed. Only the 4 commands that have registered handlers are included. Registration failure logs a warning but does not block bot startup.

🧪 Test Environment

Hardware: PC (AMD64)
OS: Ubuntu 24.04 (Linux 6.8.0-87-generic)
Model/Provider: N/A (channel-level change, no LLM interaction)
Channels: Telegram

📸 Evidence (Optional)

Click to view Logs/Screenshots

After deploying, pressing / in the Telegram chat shows the command menu with all 4 registered commands. make build and go test ./pkg/channels/ -v pass with no errors or warnings.

☑️ Checklist

My code/docs follow the style of this project.
I have performed a self-review of my own changes.
I have updated the documentation accordingly.

Call bot.SetMyCommands() on startup so that Telegram displays the command menu when users press "/" in chat. Registration failure is logged as a warning and does not block bot startup.

Copilot

Pull request overview

This PR adds Telegram command menu registration via SetMyCommands API so that users can see available commands when typing / in Telegram chat. The implementation registers the four existing command handlers (/start, /help, /show, /list) during bot startup, with registration failures logged as warnings to avoid blocking startup.

Changes:

Added registerCommands() method to register bot commands with Telegram API
Integrated command registration into Start() method with non-blocking error handling
Mapped all four existing command handlers to their descriptions for the command menu

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

pkg/channels/telegram.go

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

Copilot

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 1 comment.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

pkg/channels/telegram.go

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

Copilot

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 2 comments.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

pkg/channels/telegram.go

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

Copilot

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 1 comment.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot · 2026-02-23T03:11:19Z

pkg/channels/telegram.go

+	// Register command menu with Telegram
+	if err := c.registerCommands(ctx); err != nil {
+		logger.WarnCF("telegram", "Failed to register commands menu", map[string]any{
+			"error": err.Error(),
+		})
+	}


The command registration is happening after the bot is marked as running and after logging "Telegram bot connected". Consider moving this registration to occur before line 128 (before setRunning) and before the "connected" log message. This would ensure all initialization steps complete before the bot is considered operational and would make the "connected" log more accurate. Compare with the Discord channel implementation where bot info is fetched before opening the session.

alexhoshina · 2026-02-24T07:01:35Z

Duplicate with #300

nikolasdehor

Clean implementation. Using SetMyCommands on startup is the standard Telegram bot pattern. Good choice to log a warning on failure rather than blocking startup.

Two minor suggestions (non-blocking):

The command descriptions ("Show current configuration", "List available options") are generic. Consider aligning them with what the handlers actually do in the context of PicoClaw (e.g., "Show bot configuration and model info", "List installed skills").
If commands are ever added or changed dynamically, consider calling SetMyCommands again. But for static commands, startup registration is fine.

LGTM.

mymmrac · 2026-03-03T18:45:19Z

Closing this PR as the same was already done in #300

feat: register Telegram command menu via SetMyCommands

fa6a8f9

Call bot.SetMyCommands() on startup so that Telegram displays the command menu when users press "/" in chat. Registration failure is logged as a warning and does not block bot startup.

Copilot AI review requested due to automatic review settings February 23, 2026 02:57

Copilot started reviewing on behalf of rfschubert February 23, 2026 02:58 View session

Copilot AI reviewed Feb 23, 2026

View reviewed changes

pkg/channels/telegram.go Outdated Show resolved Hide resolved

Update pkg/channels/telegram.go

63a5997

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

Copilot AI review requested due to automatic review settings February 23, 2026 03:02

Copilot started reviewing on behalf of rfschubert February 23, 2026 03:02 View session

Copilot AI reviewed Feb 23, 2026

View reviewed changes

pkg/channels/telegram.go Show resolved Hide resolved

Update pkg/channels/telegram.go

58c1bac

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

Copilot AI review requested due to automatic review settings February 23, 2026 03:05

Copilot started reviewing on behalf of rfschubert February 23, 2026 03:06 View session

Copilot AI reviewed Feb 23, 2026

View reviewed changes

pkg/channels/telegram.go Outdated Show resolved Hide resolved

pkg/channels/telegram.go Outdated Show resolved Hide resolved

Update pkg/channels/telegram.go

04e069e

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

Copilot AI review requested due to automatic review settings February 23, 2026 03:08

Update pkg/channels/telegram.go

83ac9e6

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

Copilot started reviewing on behalf of rfschubert February 23, 2026 03:08 View session

Copilot AI reviewed Feb 23, 2026

View reviewed changes

alexhoshina mentioned this pull request Feb 23, 2026

[Refactor]: Channel System Refactoring / [Refactor]: Channel系统重构 #621

Closed

13 tasks

alexhoshina added this to the Refactor Channel milestone Feb 26, 2026

nikolasdehor approved these changes Feb 28, 2026

View reviewed changes

sipeed-bot bot added type: enhancement New feature or request domain: channel labels Mar 3, 2026

mymmrac closed this Mar 3, 2026

github-actions bot mentioned this pull request Mar 4, 2026

🦞 OpenClaw 生态日报 2026-03-04 duanyytop/agents-radar#71

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

feat: register Telegram command menu via SetMyCommands#668

feat: register Telegram command menu via SetMyCommands#668
rfschubert wants to merge 5 commits intosipeed:mainfrom
rfschubert:feat/telegram-setmycommands

rfschubert commented Feb 23, 2026 •

edited

Loading

Uh oh!

Copilot AI left a comment

Uh oh!

Uh oh!

Copilot AI left a comment

Uh oh!

Uh oh!

Copilot AI left a comment

Uh oh!

Uh oh!

Uh oh!

Copilot AI left a comment

Uh oh!

Copilot AI Feb 23, 2026

Uh oh!

alexhoshina commented Feb 24, 2026

Uh oh!

nikolasdehor left a comment

Uh oh!

mymmrac commented Mar 3, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

Conversation

rfschubert commented Feb 23, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

📝 Description

🗣️ Type of Change

🤖 AI Code Generation

🔗 Related Issue

📚 Technical Context (Skip for Docs)

🧪 Test Environment

📸 Evidence (Optional)

☑️ Checklist

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Copilot AI Feb 23, 2026

Choose a reason for hiding this comment

Uh oh!

alexhoshina commented Feb 24, 2026

Uh oh!

nikolasdehor left a comment

Choose a reason for hiding this comment

Uh oh!

mymmrac commented Mar 3, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

rfschubert commented Feb 23, 2026 •

edited

Loading