openclaw - 💡(How to fix) Fix [Bug]: Telegram CLI message send still hangs on 2026.4.29 after grammy runtime-deps fix [1 comments, 2 participants]

node -e "import('/usr/lib/node_modules/openclaw/dist/extensions/telegram/test-api.js').then(()=>console.log('TELEGRAM_IMPORT_OK')).catch(e=>{console.error(e); process.exit(1)})" 2. openclaw message send --channel telegram ... --json should either deliver through the running gateway or fail with a bounded, actionable error.

TL;DR

The issue can be mitigated by ensuring proper runtime dependency resolution for the Telegram CLI send path, potentially by adjusting the package installation or symlink configuration.

Guidance

• Verify that the grammy and @grammyjs packages are correctly installed and accessible in the global package root, as their absence seems to cause the hang issue.
• Check the plugins.load.paths config for any stale entries that might interfere with the correct loading of dependencies.
• Consider adjusting the symlink approach to ensure that the staged runtime dependencies are properly linked to the global package root, as the current method seems to only partially resolve the issue.
• Test the openclaw message send command with the --verbose flag (if available) to gather more detailed output that might help identify the exact point of failure.

Example

No specific code snippet is provided due to the lack of direct code references in the issue, but ensuring the correct installation and accessibility of grammy and @grammyjs could involve commands like:

npm install grammy @grammyjs

or adjusting symlinks to match the expected package locations.

Notes

The issue seems to be related to the way OpenClaw resolves its runtime dependencies, particularly for the Telegram CLI send path. The provided steps and symlinking approach have partially fixed related issues but do not fully resolve the problem. Further investigation into the dependency resolution mechanism and the specific requirements of the Telegram CLI send functionality is necessary.

Recommendation

Apply a workaround by manually ensuring the correct installation and accessibility of required packages like grammy and @grammyjs, and adjust the symlink configuration as needed, until a more permanent fix is available. This approach is chosen because it directly addresses the observed symptoms and allows for continued use of the OpenClaw system, albeit with manual intervention.