openclaw - 💡(How to fix) Fix [Bug] 2026.4.7: setup-entry.js specifier regression affects telegram AND slack extensions [2 comments, 3 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#62923Fetched 2026-04-09 08:00:37
View on GitHub
Comments
2
Participants
3
Timeline
4
Reactions
2
Timeline (top)
commented ×2closed ×1renamed ×1

OpenClaw 2026.4.7 ships with a build regression in setup-entry.js for at least two
bundled channel extensions (telegram and slack). The specifier paths were changed
between 2026.4.5 and 2026.4.7 to reference ./src/ files that are not included in the published npm tarball.

Related: #62880 covers the telegram side. This report adds the slack extension, root cause diff, and confirms via tarball comparison.

Root cause

In 2026.4.5, dist/extensions/telegram/setup-entry.js uses:
plugin: { specifier: "./channel-plugin-api.js", exportName: "telegramSetupPlugin" }

In 2026.4.7, it was changed to:
plugin: { specifier: "./src/channel.setup.js", exportName: "telegramSetupPlugin" }
secrets: { specifier: "./src/secret-contract.js", exportName: "channelSecrets" }

The src/ directory does not exist under dist/extensions/telegram/ in the published package. The actual compiled code lives at dist/channel.setup-DnkdT607.js
(referenced correctly by api.js and channel-plugin-api.js).

Affected extensions

telegram — missing src/channel.setup.js (was ./channel-plugin-api.js in 2026.4.5,
changed to ./src/channel.setup.js in 2026.4.7)

telegram — missing src/secret-contract.js (not referenced in 2026.4.5, added as
./src/secret-contract.js in 2026.4.7)

slack — missing src/secret-contract.js (not referenced in 2026.4.5, added as
./src/secret-contract.js in 2026.4.7)

Impact

  • Config validation fails on startup, blocking the entire gateway — not just the
    affected channels
  • openclaw doctor, openclaw plugins list, openclaw config validate all crash before they can run
  • The error fires during bootstrap scan of all bundled extensions, even disabled ones — there is no config-level workaround
  • Users upgrading from 2026.4.5 to 2026.4.7 have no working CLI to diagnose or fix the issue

Verification

Fresh install confirms the bug is in the published package, not local state:

npm uninstall -g openclaw && npm cache clean --force npm install -g [email protected]

Tarball comparison:

npm pack [email protected] && npm pack [email protected]
tar tf openclaw-2026.4.5.tgz | grep "extensions/telegram/src/" # empty tar tf openclaw-2026.4.7.tgz | grep "extensions/telegram/src/" # also empty

Both tarballs lack src/ — but only 2026.4.7's setup-entry.js references it

Workaround

Downgrade to 2026.4.5:
npm install -g [email protected]

Environment

  • OpenClaw 2026.4.7 (5050017)
  • Ubuntu Linux 6.17.0 / Node v22
  • Clean npm install (no prior symlinks or local modifications)

Error Message

  • The error fires during bootstrap scan of all bundled extensions, even disabled

Root Cause

Root cause

Fix Action

Fix / Workaround

  • Config validation fails on startup, blocking the entire gateway — not just the
    affected channels
    • openclaw doctor, openclaw plugins list, openclaw config validate all crash before they can run
    • The error fires during bootstrap scan of all bundled extensions, even disabled ones — there is no config-level workaround
    • Users upgrading from 2026.4.5 to 2026.4.7 have no working CLI to diagnose or fix the issue

Workaround

Downgrade to 2026.4.5:
npm install -g [email protected]

RAW_BUFFERClick to expand / collapse

Summary

OpenClaw 2026.4.7 ships with a build regression in setup-entry.js for at least two
bundled channel extensions (telegram and slack). The specifier paths were changed
between 2026.4.5 and 2026.4.7 to reference ./src/ files that are not included in the published npm tarball.

Related: #62880 covers the telegram side. This report adds the slack extension, root cause diff, and confirms via tarball comparison.

Root cause

In 2026.4.5, dist/extensions/telegram/setup-entry.js uses:
plugin: { specifier: "./channel-plugin-api.js", exportName: "telegramSetupPlugin" }

In 2026.4.7, it was changed to:
plugin: { specifier: "./src/channel.setup.js", exportName: "telegramSetupPlugin" }
secrets: { specifier: "./src/secret-contract.js", exportName: "channelSecrets" }

The src/ directory does not exist under dist/extensions/telegram/ in the published package. The actual compiled code lives at dist/channel.setup-DnkdT607.js
(referenced correctly by api.js and channel-plugin-api.js).

Affected extensions

telegram — missing src/channel.setup.js (was ./channel-plugin-api.js in 2026.4.5,
changed to ./src/channel.setup.js in 2026.4.7)

telegram — missing src/secret-contract.js (not referenced in 2026.4.5, added as
./src/secret-contract.js in 2026.4.7)

slack — missing src/secret-contract.js (not referenced in 2026.4.5, added as
./src/secret-contract.js in 2026.4.7)

Impact

  • Config validation fails on startup, blocking the entire gateway — not just the
    affected channels
  • openclaw doctor, openclaw plugins list, openclaw config validate all crash before they can run
  • The error fires during bootstrap scan of all bundled extensions, even disabled ones — there is no config-level workaround
  • Users upgrading from 2026.4.5 to 2026.4.7 have no working CLI to diagnose or fix the issue

Verification

Fresh install confirms the bug is in the published package, not local state:

npm uninstall -g openclaw && npm cache clean --force npm install -g [email protected]

Tarball comparison:

npm pack [email protected] && npm pack [email protected]
tar tf openclaw-2026.4.5.tgz | grep "extensions/telegram/src/" # empty tar tf openclaw-2026.4.7.tgz | grep "extensions/telegram/src/" # also empty

Both tarballs lack src/ — but only 2026.4.7's setup-entry.js references it

Workaround

Downgrade to 2026.4.5:
npm install -g [email protected]

Environment

  • OpenClaw 2026.4.7 (5050017)
  • Ubuntu Linux 6.17.0 / Node v22
  • Clean npm install (no prior symlinks or local modifications)

extent analysis

TL;DR

Downgrade to OpenClaw version 2026.4.5 to avoid the build regression in setup-entry.js for bundled channel extensions.

Guidance

  • The issue is caused by a change in specifier paths in setup-entry.js, referencing ./src/ files that are not included in the published npm tarball.
  • To verify the issue, perform a fresh install of OpenClaw 2026.4.7 and check for config validation failures on startup.
  • As a temporary workaround, downgrade to OpenClaw 2026.4.5 using npm install -g [email protected].
  • To confirm the bug is in the published package, compare the tarballs of OpenClaw 2026.4.5 and 2026.4.7 using npm pack and tar tf.

Notes

The issue is specific to OpenClaw version 2026.4.7 and affects the telegram and slack extensions. The workaround is to downgrade to version 2026.4.5.

Recommendation

Apply the workaround by downgrading to OpenClaw version 2026.4.5, as this is a known stable version that does not exhibit the build regression issue.

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