Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix Bug: OpenClaw 2026.4.7 fails to start - bundled telegram plugin entry point error [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#62918•Fetched 2026-04-09 08:00:42
View on GitHub
Comments
0
Participants
1
Timeline
0
Reactions
1
Author
vliuytvliuyt
Participants
vliuytvliuyt

Error Message

Config invalid Error: bundled plugin entry "./src/channel.setup.js" failed to open from ".../dist/extensions/telegram/setup-entry.js" (resolved ".../dist/extensions/telegram/src/channel.setup.js"): ENOENT: no such file or directory

Root Cause

The bundled plugin system is attempting to load:

  • Path: `dist/extensions/telegram/src/channel.setup.js`
  • But the file does not exist in the telegram plugin package

This suggests the bundled plugin manifest or entry point configuration is out of sync with the actual telegram plugin structure in 2026.4.7.

Fix Action

Workaround

Rolling back to OpenClaw 2026.4.5 works:

npm install -g [email protected]
openclaw gateway restart

Code Example

Config invalid
Error: bundled plugin entry "./src/channel.setup.js" failed to open from ".../dist/extensions/telegram/setup-entry.js" (resolved ".../dist/extensions/telegram/src/channel.setup.js"): ENOENT: no such file or directory

---

npm install -g openclaw@2026.4.5
openclaw gateway restart
RAW_BUFFERClick to expand / collapse

Bug Description

OpenClaw 2026.4.7 fails to start with the following error:

Config invalid
Error: bundled plugin entry "./src/channel.setup.js" failed to open from ".../dist/extensions/telegram/setup-entry.js" (resolved ".../dist/extensions/telegram/src/channel.setup.js"): ENOENT: no such file or directory

Steps to Reproduce

  1. Update to OpenClaw 2026.4.7 (e.g., `npm install -g openclaw@latest`)
  2. Run `openclaw gateway start`
  3. Gateway fails to start with the error above

Environment

  • OpenClaw Version: 2026.4.7
  • OS: macOS (Darwin)
  • Node.js: v24.13.0

Additional Context

  • The error persists even when telegram plugin is disabled or removed from `openclaw.json` config
  • Bundled plugin loading happens before config processing, so user config cannot override it
  • Telegram plugin in 2026.4.7 does not have a `src` directory - the structure appears to have changed from previous versions
  • Rolling back to 2026.4.5 resolves the issue

Analysis

The bundled plugin system is attempting to load:

  • Path: `dist/extensions/telegram/src/channel.setup.js`
  • But the file does not exist in the telegram plugin package

This suggests the bundled plugin manifest or entry point configuration is out of sync with the actual telegram plugin structure in 2026.4.7.

Workaround

Rolling back to OpenClaw 2026.4.5 works:

npm install -g [email protected]
openclaw gateway restart

extent analysis

TL;DR

Rolling back to OpenClaw version 2026.4.5 is a viable workaround to resolve the gateway startup issue.

Guidance

  • The error occurs due to a mismatch between the bundled plugin manifest and the actual telegram plugin structure in OpenClaw 2026.4.7.
  • Verify the issue by checking the file path dist/extensions/telegram/src/channel.setup.js and confirming it does not exist.
  • To mitigate the issue, roll back to a previous version of OpenClaw, such as 2026.4.5, using npm install -g [email protected].
  • After rolling back, restart the gateway using openclaw gateway restart to ensure the changes take effect.

Example

npm install -g [email protected]
openclaw gateway restart

Notes

The workaround may not be suitable for all users, especially those who rely on features or fixes introduced in version 2026.4.7. It is essential to weigh the benefits of rolling back against potential losses of functionality.

Recommendation

Apply the workaround by rolling back to OpenClaw version 2026.4.5, as it is a confirmed solution that resolves the gateway startup issue. This recommendation is based on the provided analysis and the fact that rolling back to 2026.4.5 has been verified to work.

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…
#file not found#serialization error#model compatibility#GPU setup#container setup

Still need to ship something?

×6

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

Back to top recommendations

TRENDING