openclaw - 💡(How to fix) Fix 2026.4.7: Telegram extension dist missing channel.setup.js — startup crash [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#62919Fetched 2026-04-09 08:00:41
View on GitHub
Comments
0
Participants
1
Timeline
0
Reactions
0
Participants

OpenClaw 2026.4.7 ships with a missing file in the Telegram extension dist bundle:

~/.nvm/versions/node/v24.14.0/lib/node_modules/openclaw/dist/extensions/telegram/src/channel.setup.js

This causes a hard startup crash on every CLI command, including openclaw doctor --fix.

Error Message

  1. Error: cannot find module extensions/telegram/src/channel.setup.js

Root Cause

The plugin loader evaluates the Telegram extension file before checking enabled flags in config. Disabling Telegram in openclaw.json does not prevent the crash because the loader runs first.

Fix Action

Workaround

Create a no-op stub at the missing path:

mkdir -p $(npm root -g)/openclaw/dist/extensions/telegram/src
cat > $(npm root -g)/openclaw/dist/extensions/telegram/src/channel.setup.js << 'EOF'
module.exports = { telegramSetupPlugin: { setup: () => {} } };
EOF

Note: the correct named export is telegramSetupPlugin (not setup alone).

Code Example

~/.nvm/versions/node/v24.14.0/lib/node_modules/openclaw/dist/extensions/telegram/src/channel.setup.js

---

mkdir -p $(npm root -g)/openclaw/dist/extensions/telegram/src
cat > $(npm root -g)/openclaw/dist/extensions/telegram/src/channel.setup.js << 'EOF'
module.exports = { telegramSetupPlugin: { setup: () => {} } };
EOF
RAW_BUFFERClick to expand / collapse

Summary

OpenClaw 2026.4.7 ships with a missing file in the Telegram extension dist bundle:

~/.nvm/versions/node/v24.14.0/lib/node_modules/openclaw/dist/extensions/telegram/src/channel.setup.js

This causes a hard startup crash on every CLI command, including openclaw doctor --fix.

Impact

Complete gateway failure on upgrade. No CLI commands work until the file is stubbed manually.

Steps to Reproduce

  1. npm i -g [email protected]
  2. Run any openclaw command
  3. Error: cannot find module extensions/telegram/src/channel.setup.js

Root Cause

The plugin loader evaluates the Telegram extension file before checking enabled flags in config. Disabling Telegram in openclaw.json does not prevent the crash because the loader runs first.

Workaround

Create a no-op stub at the missing path:

mkdir -p $(npm root -g)/openclaw/dist/extensions/telegram/src
cat > $(npm root -g)/openclaw/dist/extensions/telegram/src/channel.setup.js << 'EOF'
module.exports = { telegramSetupPlugin: { setup: () => {} } };
EOF

Note: the correct named export is telegramSetupPlugin (not setup alone).

Environment

  • OpenClaw: 2026.4.7
  • Node: v24.14.0
  • macOS: arm64 (Apple Silicon)
  • Telegram: disabled in config (channels.telegram.enabled: false and plugins.entries.telegram.enabled: false)

extent analysis

TL;DR

Create a no-op stub file at the missing path to prevent the startup crash.

Guidance

  • Verify the missing file path matches the one in the issue: ~/.nvm/versions/node/v24.14.0/lib/node_modules/openclaw/dist/extensions/telegram/src/channel.setup.js
  • Run the provided workaround command to create the stub file
  • Check if disabling Telegram in openclaw.json still causes issues after applying the workaround
  • Test openclaw commands after creating the stub file to ensure they work as expected

Example

The workaround command provided in the issue can be used as-is:

mkdir -p $(npm root -g)/openclaw/dist/extensions/telegram/src
cat > $(npm root -g)/openclaw/dist/extensions/telegram/src/channel.setup.js << 'EOF'
module.exports = { telegramSetupPlugin: { setup: () => {} } };
EOF

Notes

This workaround may not be necessary in future versions of OpenClaw, as it is likely a temporary fix for the missing file issue in version 2026.4.7.

Recommendation

Apply the workaround, as it provides a reliable solution to the startup crash issue until a fixed version of OpenClaw is released.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING