openclaw - 💡(How to fix) Fix v2026.4.7: Telegram extension missing src/channel.setup.js — config invalid on upgrade [1 participants]

openclaw2026-04-08 04:22:47

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#62921•Fetched 2026-04-09 08:00:38

View on GitHub

Comments

Participants

Timeline

Reactions

Author

justinbao19

Participants

justinbao19

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", reason "path"): ENOENT: no such file or directory, lstat '/opt/homebrew/lib/node_modules/openclaw/dist/extensions/telegram/src/channel.setup.js'

Root Cause

dist/extensions/telegram/setup-entry.js references ./src/channel.setup.js:

plugin: {
  specifier: "./src/channel.setup.js",
  exportName: "telegramSetupPlugin"
},

But the src/ subdirectory does not exist in the 2026.4.7 npm package. Files present in dist/extensions/telegram/:

allow-from.js, api.js, channel-config-api.js, channel-plugin-api.js,
configured-state.js, contract-api.js, index.js, openclaw.plugin.json,
package.json, runtime-api.js, secret-contract-api.js, session-key-api.js,
setup-entry.js, test-api.js, test-support.js, update-offset-runtime-api.js

No src/ directory. Looks like a packaging step that should copy src/channel.setup.js into the bundle was skipped or the path reference wasn't updated after a refactor.

Fix Action

Fix / Workaround

Any user upgrading to 2026.4.7 with Telegram configured will get a broken config on startup
openclaw doctor --fix does not resolve it
Workaround: roll back to 2026.4.5 (npm install -g [email protected])

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",
    reason "path"): ENOENT: no such file or directory,
    lstat '/opt/homebrew/lib/node_modules/openclaw/dist/extensions/telegram/src/channel.setup.js'

---

plugin: {
  specifier: "./src/channel.setup.js",
  exportName: "telegramSetupPlugin"
},

---

allow-from.js, api.js, channel-config-api.js, channel-plugin-api.js,
configured-state.js, contract-api.js, index.js, openclaw.plugin.json,
package.json, runtime-api.js, secret-contract-api.js, session-key-api.js,
setup-entry.js, test-api.js, test-support.js, update-offset-runtime-api.js

RAW_BUFFERClick to expand / collapse

Bug Report

OpenClaw version: 2026.4.7 (5050017) Previous version: 2026.4.5 (3e72c03) — working fine OS: macOS 15 (arm64), installed via npm install -g openclaw

Problem

After upgrading from 2026.4.5 to 2026.4.7, openclaw status fails immediately with:

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",
    reason "path"): ENOENT: no such file or directory,
    lstat '/opt/homebrew/lib/node_modules/openclaw/dist/extensions/telegram/src/channel.setup.js'

Root Cause

dist/extensions/telegram/setup-entry.js references ./src/channel.setup.js:

plugin: {
  specifier: "./src/channel.setup.js",
  exportName: "telegramSetupPlugin"
},

But the src/ subdirectory does not exist in the 2026.4.7 npm package. Files present in dist/extensions/telegram/:

allow-from.js, api.js, channel-config-api.js, channel-plugin-api.js,
configured-state.js, contract-api.js, index.js, openclaw.plugin.json,
package.json, runtime-api.js, secret-contract-api.js, session-key-api.js,
setup-entry.js, test-api.js, test-support.js, update-offset-runtime-api.js

No src/ directory. Looks like a packaging step that should copy src/channel.setup.js into the bundle was skipped or the path reference wasn't updated after a refactor.

Impact

Any user upgrading to 2026.4.7 with Telegram configured will get a broken config on startup
openclaw doctor --fix does not resolve it
Workaround: roll back to 2026.4.5 (npm install -g [email protected])

Steps to Reproduce

Have Telegram configured in ~/.openclaw/openclaw.json
npm install -g [email protected]
Run openclaw status
See config invalid error

Expected Behavior

Upgrade completes without breaking Telegram channel config.

extent analysis

TL;DR

The most likely fix is to wait for a corrected version of OpenClaw that properly includes the src/channel.setup.js file or updates the reference in setup-entry.js to point to the correct location of the channel.setup.js file.

Guidance

Verify the issue by checking the files present in the dist/extensions/telegram/ directory to confirm the absence of the src/ subdirectory and the channel.setup.js file.
Consider rolling back to version 2026.4.5 using npm install -g [email protected] as a temporary workaround to restore functionality.
Monitor the OpenClaw project for an update that addresses this packaging issue, as it is likely a mistake in the build or packaging process.
If possible, manually inspect the setup-entry.js file to see if the reference to ./src/channel.setup.js can be updated to point to a correct location, although this might require a deeper understanding of the OpenClaw internals.

Example

No code snippet is provided as the issue seems to be related to packaging and not a code-level problem that can be fixed with a simple snippet.

Notes

The root cause appears to be a packaging error where a necessary file (src/channel.setup.js) is not included in the distribution, or its path reference in setup-entry.js is incorrect. This suggests a build or deployment issue rather than a problem with the code itself.

Recommendation

Apply the workaround by rolling back to version 2026.4.5 until a corrected version of OpenClaw is released, as this is the safest and most straightforward way to restore functionality without waiting for an official fix.

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?

#api #ISR setup #authentication setup #request error #file not found

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 v2026.4.7: Telegram extension missing src/channel.setup.js — config invalid on upgrade [1 participants]

Recommended Tools

GitHub issue graph ai analysis

Error Message

Root Cause

Fix Action

Fix / Workaround

Code Example

Bug Report

Problem

Root Cause

Impact

Steps to Reproduce

Expected Behavior

extent analysis

TL;DR

Guidance

Example

Notes

Recommendation

Still need to ship something?

TRENDING

openclaw - 💡(How to fix) Fix v2026.4.7: Telegram extension missing src/channel.setup.js — config invalid on upgrade [1 participants]

Recommended Tools

GitHub issue graph ai analysis

Error Message

Root Cause

Fix Action

Fix / Workaround

Code Example

Bug Report

Problem

Root Cause

Impact

Steps to Reproduce

Expected Behavior

extent analysis

TL;DR

Guidance

Example

Notes

Recommendation

Still need to ship something?

RELATED_DISCOVERY

TRENDING