openclaw - 💡(How to fix) Fix bug: Telegram plugin missing src/channel.setup.js in v2026.4.7 and v2026.4.8 — gateway fails to start [2 comments, 3 participants]

openclaw2026-04-08 13:52:03

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.

GitHub issue URL

Helpful · Quick feedback

GitHub stats

openclaw/openclaw#63179•Fetched 2026-04-09 07:57:24

View on GitHub

Comments

Participants

Timeline

Reactions

Author

Participants

Timeline (top)

commented ×2

After upgrading to v2026.4.7 (and confirmed also in v2026.4.8), the gateway fails to start with the following error:

Config invalid
File: ~/.openclaw/openclaw.json
Problem:
  - <root>: read failed: Error: bundled plugin entry "./src/channel.setup.js" failed to open from "/opt/homebrew/lib/node_modules/openclaw/dist/extensions/telegram/setup-entry.js" (resolved "/opt/homebrew/lib/node_modules/openclaw/dist/extensions/telegram/src/channel.setup.js", plugin root "/opt/homebrew/lib/node_modules/openclaw/dist/extensions/telegram", reason "path"): ENOENT: no such file or directory, lstat '/opt/homebrew/lib/node_modules/openclaw/dist/extensions/telegram/src/channel.setup.js'

Error Message

Config invalid File: ~/.openclaw/openclaw.json Problem:

<root>: read failed: Error: bundled plugin entry "./src/channel.setup.js" failed to open from "/opt/homebrew/lib/node_modules/openclaw/dist/extensions/telegram/setup-entry.js" (resolved "/opt/homebrew/lib/node_modules/openclaw/dist/extensions/telegram/src/channel.setup.js", plugin root "/opt/homebrew/lib/node_modules/openclaw/dist/extensions/telegram", reason "path"): ENOENT: no such file or directory, lstat '/opt/homebrew/lib/node_modules/openclaw/dist/extensions/telegram/src/channel.setup.js'

Root Cause

setup-entry.js references ./src/channel.setup.js but the src/ subdirectory is not present in the published npm package for either v2026.4.7 or v2026.4.8.

The file /opt/homebrew/lib/node_modules/openclaw/dist/extensions/telegram/setup-entry.js contains:

var setup_entry_default = defineBundledChannelSetupEntry({
  importMetaUrl: import.meta.url,
  plugin: {
    specifier: "./src/channel.setup.js",  // <-- this file is missing
    exportName: "telegramSetupPlugin"
  },
  ...
});

Running ls dist/extensions/telegram/ confirms no src/ directory is present in either affected release.

Fix Action

Workaround

Roll back to v2026.4.5:

npm install -g [email protected]
openclaw gateway restart

Code Example

Config invalid
File: ~/.openclaw/openclaw.json
Problem:
  - <root>: read failed: Error: bundled plugin entry "./src/channel.setup.js" failed to open from "/opt/homebrew/lib/node_modules/openclaw/dist/extensions/telegram/setup-entry.js" (resolved "/opt/homebrew/lib/node_modules/openclaw/dist/extensions/telegram/src/channel.setup.js", plugin root "/opt/homebrew/lib/node_modules/openclaw/dist/extensions/telegram", reason "path"): ENOENT: no such file or directory, lstat '/opt/homebrew/lib/node_modules/openclaw/dist/extensions/telegram/src/channel.setup.js'

---

var setup_entry_default = defineBundledChannelSetupEntry({
  importMetaUrl: import.meta.url,
  plugin: {
    specifier: "./src/channel.setup.js",  // <-- this file is missing
    exportName: "telegramSetupPlugin"
  },
  ...
});

---

npm install -g openclaw@2026.4.5
openclaw gateway restart

RAW_BUFFERClick to expand / collapse

Description

After upgrading to v2026.4.7 (and confirmed also in v2026.4.8), the gateway fails to start with the following error:

Config invalid
File: ~/.openclaw/openclaw.json
Problem:
  - <root>: read failed: Error: bundled plugin entry "./src/channel.setup.js" failed to open from "/opt/homebrew/lib/node_modules/openclaw/dist/extensions/telegram/setup-entry.js" (resolved "/opt/homebrew/lib/node_modules/openclaw/dist/extensions/telegram/src/channel.setup.js", plugin root "/opt/homebrew/lib/node_modules/openclaw/dist/extensions/telegram", reason "path"): ENOENT: no such file or directory, lstat '/opt/homebrew/lib/node_modules/openclaw/dist/extensions/telegram/src/channel.setup.js'

Root Cause

setup-entry.js references ./src/channel.setup.js but the src/ subdirectory is not present in the published npm package for either v2026.4.7 or v2026.4.8.

The file /opt/homebrew/lib/node_modules/openclaw/dist/extensions/telegram/setup-entry.js contains:

var setup_entry_default = defineBundledChannelSetupEntry({
  importMetaUrl: import.meta.url,
  plugin: {
    specifier: "./src/channel.setup.js",  // <-- this file is missing
    exportName: "telegramSetupPlugin"
  },
  ...
});

Running ls dist/extensions/telegram/ confirms no src/ directory is present in either affected release.

Steps to Reproduce

npm install -g [email protected] (or @2026.4.8)
openclaw gateway restart
Gateway fails immediately with the ENOENT error above
openclaw doctor --fix does not resolve it

Workaround

Roll back to v2026.4.5:

npm install -g [email protected]
openclaw gateway restart

Environment

macOS (arm64)
Node v22.22.0
Install path: /opt/homebrew/lib/node_modules/openclaw
Channel: Telegram
Affects: v2026.4.7, v2026.4.7-1, v2026.4.8 (all confirmed broken)
Working: v2026.4.5

extent analysis

TL;DR

The most likely fix is to roll back to a working version of openclaw, such as v2026.4.5, due to a missing file in the published npm packages of affected versions.

Guidance

The error occurs because the src/ subdirectory and specifically channel.setup.js are missing from the npm packages of openclaw versions v2026.4.7 and v2026.4.8.
To verify the issue, check the presence of the src/ directory and its contents in the installed openclaw package.
As a workaround, downgrade openclaw to a version known to work, such as v2026.4.5, using npm install -g [email protected].
After downgrading, restart the gateway with openclaw gateway restart to ensure it starts correctly.

Example

No code snippet is necessary for this solution, as it involves changing the version of openclaw rather than modifying code.

Notes

This solution assumes that downgrading to v2026.4.5 does not introduce other compatibility issues or security vulnerabilities. It's essential to monitor for any other problems after applying this workaround.

Recommendation

Apply the workaround by downgrading to v2026.4.5, as it is a confirmed working version that avoids the ENOENT error caused by the missing channel.setup.js file.

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?

#orchestration issue #cache issue #memory leak #API versioning #request timeout

Still need to ship something?

×6

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

Data

Security

Network

Code

UI/UX

Text

System

Multimedia

Protocol

API

Engineering

openclaw - 💡(How to fix) Fix bug: Telegram plugin missing src/channel.setup.js in v2026.4.7 and v2026.4.8 — gateway fails to start [2 comments, 3 participants]

Recommended Tools

GitHub issue graph ai analysis

Error Message

Root Cause

Fix Action

Workaround

Code Example

Description

Root Cause

Steps to Reproduce

Workaround

Environment

extent analysis

TL;DR

Guidance

Example

Notes

Recommendation

Still need to ship something?

TRENDING

openclaw - 💡(How to fix) Fix bug: Telegram plugin missing src/channel.setup.js in v2026.4.7 and v2026.4.8 — gateway fails to start [2 comments, 3 participants]

Recommended Tools

GitHub issue graph ai analysis

Error Message

Root Cause

Fix Action

Workaround

Code Example

Description

Root Cause

Steps to Reproduce

Workaround

Environment

extent analysis

TL;DR

Guidance

Example

Notes

Recommendation

Still need to ship something?

RELATED_DISCOVERY

TRENDING