Updated to 2026.4.7 and config invalid openclaw.json | Friends of the Crustacean 🦞🤝 | Page 1

lilac cove Apr 8, 2026, 3:33 AM

#

I still didn't managed to find a solution.

Failed to read config at /Users/teodoro/.openclaw/openclaw.json Error: bundled plugin entry

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'

tight lynxBOT Apr 8, 2026, 3:33 AM

#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

scenic kelpBOT Apr 8, 2026, 3:36 AM

#

You’re not crazy — this looks like a packaged plugin artifact regression, not a bad JSON config.

setup-entry.js is trying to load ./src/channel.setup.js, but that file is missing in your installed bundle (/opt/homebrew/lib/node_modules/openclaw/dist/extensions/telegram/...).

Try this exact recovery path:

openclaw --version
openclaw doctor --fix
openclaw gateway restart

If it still throws the same bundled plugin entry "./src/channel.setup.js" error, move to a build with the fix (or temporarily use dev):

openclaw update --channel dev

#

openclaw gateway restart

If you prefer not to run dev, rollback to the last working tag, then restart:

openclaw update --tag <previous-working-version>
openclaw gateway restart

If you paste output of:

openclaw --version
openclaw update status

#

openclaw status --all

I can give you the exact safest version target.
Docs: https://docs.openclaw.ai/cli/update · https://docs.openclaw.ai/gateway/troubleshooting

grave garnet Apr 8, 2026, 3:42 AM

#

We're looking into this

scenic kelpBOT Apr 8, 2026, 3:42 AM

#

Yep — this is a real regression, not your config file. 🦐
2026.4.7 can ship Telegram setup with a missing bundled path (./src/channel.setup.js).

While the fix is being finalized, quickest unblock is either:

openclaw update --channel dev
openclaw gateway restart

or rollback to your last known-good version:

openclaw update --tag <last-working-version>
openclaw gateway restart

#

If you want, paste openclaw --version and I’ll suggest the safest exact rollback target.

lilac cove Apr 8, 2026, 3:43 AM

#

openclaw --version
OpenClaw 2026.4.7 (5050017)

openclaw update status
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'

Run: openclaw doctor --fix

openclaw update --channel dev
Config invalid
File: ~/.openclaw/openclaw.json
Problem: ...

openclaw update --tag 2026.4.5
Config invalid
File: ~/.openclaw/openclaw.json
Problem:

neither updates are working

scenic kelpBOT Apr 8, 2026, 3:45 AM

#

Got it — this is why your updates fail: openclaw update validates your current config first, and your current config load is crashing before update can run.

Use a temporary clean config path just for the update command:

cp ~/.openclaw/openclaw.json ~/.openclaw/openclaw.json.bak

cat > /tmp/openclaw-recovery.json <<'EOF'
{}
EOF

OPENCLAW_CONFIG_PATH=/tmp/openclaw-recovery.json openclaw update --tag main
openclaw gateway restart

Then test normal config again:

#

openclaw status --all

If it still fails, paste the plugins section from ~/.openclaw/openclaw.json (redact secrets) — I’ll tell you exactly what key to remove.
Most likely there’s a stale plugins.entries.telegram source/path pointing to .../setup-entry.js.

If this unblocks you, please mark the solution so it gets indexed on Answer Overflow 🙌

trail cosmos Apr 8, 2026, 3:50 AM

#

got same issue

scenic kelpBOT Apr 8, 2026, 3:51 AM

#

Yep, same root cause — 2026.4.7 regression with Telegram setup entry.

Since openclaw update ... is blocked by config validation, use package manager directly (bypasses that path) and roll back to 2026.4.5:

pnpm add -g openclaw@2026.4.5
# if you installed with npm instead:
# npm install -g openclaw@2026.4.5

Then:

openclaw --version
openclaw gateway restart

#

2026.4.5 is available on npm and is the quickest unblock right now.

dawn flicker Apr 8, 2026, 3:59 AM

#

Failed to install bundled plugin runtime deps: Error: npm install failed

scenic kelpBOT Apr 8, 2026, 4:00 AM

#

Yep — same regression cluster.

If you now also see Failed to install bundled plugin runtime deps: npm install failed, skip doctor --fix for now and use one of these two paths:

A) Fastest stable unblock (recommended):

pnpm add -g openclaw@2026.4.5
openclaw gateway restart

B) If global npm/pnpm install keeps failing, switch to git install (bypasses this packaging/runtime-deps mess):

curl -fsSL https://openclaw.ai/install.sh | bash -s -- --install-method git
openclaw gateway restart

Then verify:

#

openclaw --version
openclaw status

If either command fails, paste the last 30 lines of output and I’ll pinpoint the exact next step.

dawn flicker Apr 8, 2026, 4:20 AM

#

Still failed to install

scenic kelpBOT Apr 8, 2026, 4:21 AM

#

Got it — let’s do a hard bypass of the broken bundled-plugin loader first, then downgrade.

Run exactly:

OPENCLAW_DISABLE_BUNDLED_PLUGINS=1 openclaw update --tag 2026.4.5 --yes
OPENCLAW_DISABLE_BUNDLED_PLUGINS=1 openclaw gateway restart
openclaw --version

Why this works: OPENCLAW_DISABLE_BUNDLED_PLUGINS=1 prevents loading the broken Telegram bundled entry just for that command run.

If this still fails, paste the full output of that first command (not truncated) and I’ll give the next exact command.

paper bronze Apr 8, 2026, 4:23 AM

#

i think i need uninstall it and reinstall it

scenic kelpBOT Apr 8, 2026, 4:23 AM

#

Yep — clean reinstall is a good move here.
Your config file stays in ~/.openclaw/openclaw.json, so this won’t wipe your setup.

Try this:

openclaw gateway stop

pnpm remove -g openclaw
pnpm add -g openclaw@2026.4.5

openclaw --version
openclaw gateway start

If you installed with npm (not pnpm), use:

#

npm uninstall -g openclaw
npm install -g openclaw@2026.4.5

If global install still fails, use git install as fallback:
https://docs.openclaw.ai/install/installer (use --install-method git).

lilac cove Apr 8, 2026, 10:29 AM

#

updated via curl one-liner script.
version 2024.4.8 fixed! ✅

Everything good! 🦞

#Updated to 2026.4.7 and config invalid openclaw.json