openclaw - 💡(How to fix) Fix [Bug]: Telegram extension setup entry points to non-existent src path in v2026.4.7 [1 comments, 2 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#63184Fetched 2026-04-09 07:57:21
View on GitHub
Comments
1
Participants
2
Timeline
1
Reactions
1
Timeline (top)
commented ×1

In OpenClaw version 2026.4.7, the Telegram extension fails to load because the setup-entry.js file contains incorrect paths pointing to a non-existent ./src/ directory within the dist package.

Error Message

Error Log

Failed to read config at /home/ubuntu/.openclaw/openclaw.json Error: bundled plugin entry "./src/channel.setup.js" failed to open from ".../dist/extensions/telegram/setup-entry.js" (resolved

Root Cause

Description

In OpenClaw version 2026.4.7, the Telegram extension fails to load because the setup-entry.js file contains incorrect paths pointing to a non-existent ./src/ directory within the dist package.

Fix Action

Resolution

Updating to version 2026.4.8 resolves this issue, as the paths have been corrected to point to the valid -api.js files.

RAW_BUFFERClick to expand / collapse

Description

In OpenClaw version 2026.4.7, the Telegram extension fails to load because the setup-entry.js file contains incorrect paths pointing to a non-existent ./src/ directory within the dist package.

Error Log

Failed to read config at /home/ubuntu/.openclaw/openclaw.json 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", plugin root ".../dist/extensions/telegram", reason "path"): ENOENT: no such file or directory, lstat '.../dist/extensions/telegram/src/channel.setup.js'

Details

In dist/extensions/telegram/setup-entry.js:

  • plugin.specifier was incorrectly set to ./src/channel.setup.js
  • secrets.specifier was incorrectly set to ./src/secret-contract.js

Resolution

Updating to version 2026.4.8 resolves this issue, as the paths have been corrected to point to the valid -api.js files.

extent analysis

TL;DR

Updating to OpenClaw version 2026.4.8 is likely to fix the issue with the Telegram extension failing to load due to incorrect paths in the setup-entry.js file.

Guidance

  • Verify that the setup-entry.js file in the dist/extensions/telegram directory contains the incorrect paths ./src/channel.setup.js and ./src/secret-contract.js.
  • Check if updating to version 2026.4.8 is feasible in your current environment.
  • If updating is not possible, consider manually correcting the paths in setup-entry.js to point to the valid files, although this is not explicitly recommended in the issue.
  • Ensure that after applying the fix, the Telegram extension loads correctly and functions as expected.

Example

No code snippet is provided as the issue does not require a code change from the user's perspective, but rather an update to a newer version of OpenClaw.

Notes

The provided solution assumes that updating to version 2026.4.8 does not introduce other compatibility issues or breaking changes in your specific setup.

Recommendation

Upgrade to OpenClaw version 2026.4.8, as it is explicitly stated that this version resolves the issue with the incorrect paths in the setup-entry.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?
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