Re-enable Telegram bot menu by default

README.md

@@ -178,7 +178,8 @@ The startup script `setup-hf-config.mjs` reads the following from **Secrets** or
 | `OPENCLAW_TELEGRAM_DISABLE_AUTO_SELECT_FAMILY` | `channels.telegram.network.autoSelectFamily=false` | Existing OpenClaw workaround for Telegram network failures on some hosts |
 | `OPENCLAW_TELEGRAM_DNS_RESULT_ORDER` | `channels.telegram.network.dnsResultOrder` | Existing OpenClaw Telegram network workaround; default `ipv4first` |
 | `OPENCLAW_TELEGRAM_PROXY` | `channels.telegram.proxy` | Optional SOCKS/HTTP proxy URL for Telegram Bot API calls |
-| Telegram command menu | `channels.telegram.commands.native = off` | This HF wrapper disables Telegram command-menu registration to reduce noisy `setMyCommands` retries on constrained hosts |
+| `OPENCLAW_TELEGRAM_NATIVE_COMMANDS` | `channels.telegram.commands.native` | `1` / `0`; default is enabled so the bot menu can appear |
+| `OPENCLAW_TELEGRAM_NATIVE_SKILLS` | `channels.telegram.commands.nativeSkills` | `1` / `0`; defaults to the same value as native commands |
 | `OPENCLAW_STARTUP_NOTIFY` | startup notify helper | `1` / `0`; send a best-effort Telegram startup notification |
 | `OPENCLAW_STARTUP_NOTIFY_TELEGRAM_TO` | startup notify helper | Optional explicit Telegram chat id; defaults to first `OPENCLAW_TELEGRAM_ALLOW_FROM` entry |
 | `OPENCLAW_TELEGRAM_API_HOST` | startup notify helper | Optional alternate Telegram Bot API host; default `api.telegram.org` |

TELEGRAM_SUPABASE_STATUS.md

@@ -25,6 +25,14 @@
 - `OPENCLAW_TELEGRAM_INIT_NOTIFY_CHAT_IDS=1083910061`
 - `OPENCLAW_STARTUP_NOTIFY_TELEGRAM_TO=1083910061`
 
+### Bot menu
+
+- Earlier versions of this HF wrapper forced `channels.telegram.commands.native = false`, which hid the Telegram bot menu.
+- The current fix changes that behavior so native Telegram commands are enabled by default again.
+- Optional overrides:
+  - `OPENCLAW_TELEGRAM_NATIVE_COMMANDS=1|0`
+  - `OPENCLAW_TELEGRAM_NATIVE_SKILLS=1|0`
+
 ### How Telegram is currently made to work on HF Space
 
 1. The container resolves `api.telegram.org` during startup.

setup-hf-config.mjs

@@ -360,6 +360,8 @@ const telegramInitNotifyChatIds = dedupe([
   ...parseCsv(process.env.OPENCLAW_STARTUP_NOTIFY_TELEGRAM_TO?.trim()),
   ...telegramAllowFrom,
 ]);
+const telegramNativeCommands = parseBoolean(process.env.OPENCLAW_TELEGRAM_NATIVE_COMMANDS);
+const telegramNativeSkills = parseBoolean(process.env.OPENCLAW_TELEGRAM_NATIVE_SKILLS);
 const telegramDisableAutoSelectFamily = parseBoolean(process.env.OPENCLAW_TELEGRAM_DISABLE_AUTO_SELECT_FAMILY);
 const telegramEnableAutoSelectFamily = parseBoolean(process.env.OPENCLAW_TELEGRAM_ENABLE_AUTO_SELECT_FAMILY);
 const telegramDnsResultOrder = process.env.OPENCLAW_TELEGRAM_DNS_RESULT_ORDER?.trim();
@@ -466,9 +468,9 @@ if (
     config.channels.telegram.groups["*"].requireMention = telegramRequireMention;
   }
   if (!config.channels.telegram.commands) config.channels.telegram.commands = {};
-  // Reduce startup noise on constrained hosts: disable Telegram command-menu registration.
-  config.channels.telegram.commands.native = false;
-  config.channels.telegram.commands.nativeSkills = false;
+  config.channels.telegram.commands.native = telegramNativeCommands ?? true;
+  config.channels.telegram.commands.nativeSkills =
+    telegramNativeSkills ?? config.channels.telegram.commands.native;
   if (!config.channels.telegram.network) config.channels.telegram.network = {};
   // HF Spaces often behave better with IPv4-only family selection for Telegram Bot API.
   if (telegramDisableAutoSelectFamily === true) {