Summary

openclaw@2026.3.31 appears to ship a package/runtime layout where bundled plugins are loadable from dist/extensions/*, but required runtime dependencies for at least some plugins are not present in the published npm package metadata/tarball.

On Android/OpenClaw-Module, updating from stable 2026.3.28 to 2026.3.31 caused plugin load failures immediately after startup. Rolling back to 2026.3.28 restored normal behavior.

First failure from runtime log

[gateway] [plugins] telegram failed to load from /data/adb/openclaw/node/lib/node_modules/openclaw/dist/extensions/telegram/index.js: Error: Cannot find module 'grammy'
Require stack:
- /data/adb/openclaw/node/lib/node_modules/openclaw/dist/sticker-cache-1Tf7t-45.js

Also observed:

[plugins] amazon-bedrock failed to load ... Error: Cannot find module '@aws-sdk/client-bedrock'

What I checked

1) Published package metadata

npm view openclaw@2026.3.31 version dependencies optionalDependencies bundledDependencies --json

Observed from the published package / packed tarball:

• dependencies: no grammy
• dependencies: no @aws-sdk/client-bedrock
• optionalDependencies: no grammy
• optionalDependencies: no @aws-sdk/client-bedrock
• no bundleDependencies / bundledDependencies

2) Packed npm tarball

• npm pack openclaw@2026.3.31
• unpacked tarball and inspected package/package.json
• grep over unpacked package tree for:
  • grammy
  • @aws-sdk/client-bedrock

Result:

• no matching dependency declarations
• no direct refs in the packed tree from the audit grep
• dist/extensions/telegram/index.js is still present and exports the Telegram plugin entrypoint

Why this looks like an upstream packaging/build issue

This does not look like a local updater-only problem:

• the failure appeared immediately on the updated runtime
• rollback to 2026.3.28 restored normal behavior
• the published npm package for 2026.3.31 itself appears not to carry the missing runtime deps in package metadata

So the likely failure mode is one of:

1. published npm package missing runtime dependency declarations for bundled plugins
2. build output/chunking in 2026.3.31 now expects external deps that are not declared/bundled in the release package

Expected behavior

If bundled channel/provider plugins are shipped in the npm package, the published package should either:

• declare the needed runtime dependencies, or
• bundle them reliably, or
• guard plugin activation so missing optional deps do not break normal startup/channel loading

Environment

• OpenClaw stable before update: 2026.3.28
• Broken version tested: 2026.3.31
• Host: Android ARM64 OpenClaw-Module runtime

Impact

Telegram channel failed to load after update; Amazon Bedrock plugin also emitted missing-module errors.

If helpful, I can also provide the exact package-audit commands/results used above.