openclaw - 💡(How to fix) Fix Bundled plugins telegram and amazon-bedrock fail to load after upgrade to 2026.3.31 due to missing runtime modules [2 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#59027Fetched 2026-04-08 02:29:41
View on GitHub
Comments
2
Participants
2
Timeline
5
Reactions
2
Timeline (top)
commented ×2subscribed ×2unsubscribed ×1

Error Message

[plugins] telegram failed to load from <openclaw>/dist/extensions/telegram/index.js: Error: Cannot find module 'grammy' Require stack:

  • <openclaw>/dist/sticker-cache-*.js

Root Cause

Why this looks suspicious

This does not look like a Telegram bot config problem or Bedrock credential problem, because both failures happen at plugin load time with missing module errors.

Fix Action

Fix / Workaround

Questions

  1. Is this a known regression in 2026.3.31?
  2. Is there an official best-practice recovery path for missing bundled plugin runtime deps?
  3. Should these dependencies be present automatically for bundled plugins in a normal global install?
  4. If not a regression, what should be checked to restore plugin runtime deps cleanly without manual patching inside the package tree?

Code Example

[plugins] telegram failed to load from <openclaw>/dist/extensions/telegram/index.js: Error: Cannot find module 'grammy'
Require stack:
- <openclaw>/dist/sticker-cache-*.js

---

[plugins] amazon-bedrock failed to load from <openclaw>/dist/extensions/amazon-bedrock/index.js: Error: Cannot find module '@aws-sdk/client-bedrock'
Require stack:
- <openclaw>/dist/discovery-*.js

---

OpenClaw 2026.3.31

[plugins] amazon-bedrock failed to load from <openclaw>/dist/extensions/amazon-bedrock/index.js: Error: Cannot find module '@aws-sdk/client-bedrock'
Require stack:
- <openclaw>/dist/discovery-*.js

[plugins] telegram failed to load from <openclaw>/dist/extensions/telegram/index.js: Error: Cannot find module 'grammy'
Require stack:
- <openclaw>/dist/sticker-cache-*.js

Plugins
- Loaded: 41
- Disabled: 42
- Errors: 2
  - amazon-bedrock
  - telegram

Plugin diagnostics
- ERROR amazon-bedrock: failed to load plugin: Error: Cannot find module '@aws-sdk/client-bedrock'
- ERROR telegram: failed to load plugin: Error: Cannot find module 'grammy'
RAW_BUFFERClick to expand / collapse

Hi — reporting what may be a bundled plugin runtime dependency / packaging regression, or a missing documented recovery path.

After upgrading to OpenClaw 2026.3.31, two bundled plugins fail to load on this installation:

  • telegram
  • amazon-bedrock

Symptoms

Errors reported:

[plugins] telegram failed to load from <openclaw>/dist/extensions/telegram/index.js: Error: Cannot find module 'grammy'
Require stack:
- <openclaw>/dist/sticker-cache-*.js
[plugins] amazon-bedrock failed to load from <openclaw>/dist/extensions/amazon-bedrock/index.js: Error: Cannot find module '@aws-sdk/client-bedrock'
Require stack:
- <openclaw>/dist/discovery-*.js

openclaw doctor output (sanitized)

OpenClaw 2026.3.31

[plugins] amazon-bedrock failed to load from <openclaw>/dist/extensions/amazon-bedrock/index.js: Error: Cannot find module '@aws-sdk/client-bedrock'
Require stack:
- <openclaw>/dist/discovery-*.js

[plugins] telegram failed to load from <openclaw>/dist/extensions/telegram/index.js: Error: Cannot find module 'grammy'
Require stack:
- <openclaw>/dist/sticker-cache-*.js

Plugins
- Loaded: 41
- Disabled: 42
- Errors: 2
  - amazon-bedrock
  - telegram

Plugin diagnostics
- ERROR amazon-bedrock: failed to load plugin: Error: Cannot find module '@aws-sdk/client-bedrock'
- ERROR telegram: failed to load plugin: Error: Cannot find module 'grammy'

What was tried

  • upgrade/reinstall to 2026.3.31
  • rerun doctor / inspect plugin diagnostics
  • verify this is not limited to one plugin: both bundled plugins fail with missing runtime modules
  • review changelog for 2026.3.31, which appears to touch plugin/runtime/install/packaging behavior

Why this looks suspicious

This does not look like a Telegram bot config problem or Bedrock credential problem, because both failures happen at plugin load time with missing module errors.

That makes this look more like one of:

  1. bundled plugin runtime deps not being staged correctly
  2. changed plugin/runtime packaging behavior in 2026.3.31
  3. a documented repair step that I missed after update

Questions

  1. Is this a known regression in 2026.3.31?
  2. Is there an official best-practice recovery path for missing bundled plugin runtime deps?
  3. Should these dependencies be present automatically for bundled plugins in a normal global install?
  4. If not a regression, what should be checked to restore plugin runtime deps cleanly without manual patching inside the package tree?

Environment

  • OpenClaw version: 2026.3.31
  • Install method: global npm install
  • Reinstall of the same version did not resolve the issue
  • Failure occurs during plugin loading, before normal plugin use

Happy to provide more sanitized diagnostics if needed.

extent analysis

TL;DR

The issue can likely be resolved by ensuring the missing dependencies 'grammy' and '@aws-sdk/client-bedrock' are properly installed or bundled with the OpenClaw plugins.

Guidance

  • Verify the package.json file of the OpenClaw project to check if the missing dependencies 'grammy' and '@aws-sdk/client-bedrock' are listed.
  • Check the OpenClaw documentation for any specific instructions on handling plugin dependencies in version 2026.3.31.
  • Run npm install or npm update to ensure all dependencies are up-to-date, although this may not directly resolve the issue if the dependencies are not properly bundled with the plugins.
  • Consider reaching out to the OpenClaw support or community to confirm if this is a known regression in 2026.3.31 and to obtain an official recovery path.

Example

No specific code snippet can be provided without more information on the project structure and the exact requirements of the OpenClaw plugins.

Notes

The issue seems to be related to the packaging or dependency management of the OpenClaw plugins, specifically with the 'telegram' and 'amazon-bedrock' plugins. The fact that reinstalling the same version did not resolve the issue suggests that the problem might be with how the dependencies are handled in the 2026.3.31 version.

Recommendation

Apply a workaround by manually installing the missing dependencies 'grammy' and '@aws-sdk/client-bedrock' using npm, if they are not already installed, and then verify if the plugins can be loaded successfully. However, this should be done with caution and ideally after confirming with the OpenClaw community or support that this is an appropriate solution.

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