openclaw - 💡(How to fix) Fix [Bug]: Telegram slash commands break after update to 2026.4.21 [1 comments, 2 participants]

TL;DR

The issue can likely be fixed by checking the file path and hash in the Telegram logs to ensure they match the actual file location and hash in the OpenClaw installation.

Guidance

• Verify that the file /usr/lib/node_modules/openclaw/dist/extensions/telegram/bot-native-commands.runtime-<hash>.js exists and the hash matches the one in the error log.
• Check if there are any changes in the file structure or naming conventions between OpenClaw versions 2026.4.15 and 2026.4.21 that could cause the import error.
• Review the related issues (#69858, #69837, #69923) to see if they provide any insights into the problem or potential solutions.
• Consider reaching out to the OpenClaw community or support team for further assistance, as this issue may be specific to the library or its interaction with Telegram.

Example

No code snippet is provided as the issue seems to be related to a specific library and its configuration rather than a code error.

Notes

The issue seems to be specific to the OpenClaw library and its interaction with Telegram, and the provided information does not give a clear indication of the root cause. Further investigation and potentially reaching out to the library's support team may be necessary to resolve the issue.

Recommendation

Apply workaround: Given the information provided, it's likely that a workaround or a fix specific to the OpenClaw library and its version 2026.4.21 is needed, rather than an upgrade to a different version. The reason is that rolling back to version 2026.4.15 fixes the issue, indicating a potential regression or compatibility problem in the newer version.