Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix openclaw update fails on 2026.4.20 with missing grammy in Telegram bundled runtime [5 comments, 6 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#69837•Fetched 2026-04-22 07:47:43
View on GitHub
Comments
5
Participants
6
Timeline
14
Reactions
4
Author
C-mradeC-mrade
Participants
C-mradeC-mradedarealgegedarealgegejsompisjsompispbolingpbolingsteipetesteipeteStephonomonStephonomon
Timeline (top)
cross-referenced ×8commented ×5closed ×1

openclaw update upgrades successfully to 2026.4.20, but the post-update openclaw doctor check fails because the installed global package cannot resolve grammy from the bundled Telegram extension.

Error Message

Error: Cannot find module 'grammy' Require stack:

  • /home/emanu/.local/lib/node_modules/openclaw/dist/extensions/telegram/allowed-updates-BD2bJyzD.js

Root Cause

Summary

openclaw update upgrades successfully to 2026.4.20, but the post-update openclaw doctor check fails because the installed global package cannot resolve grammy from the bundled Telegram extension.

Fix Action

Fix / Workaround

Verified workaround

Running this manually inside the installed global package repairs the install:

Code Example

openclaw update

---

Error: Cannot find module 'grammy'
Require stack:
- /home/emanu/.local/lib/node_modules/openclaw/dist/extensions/telegram/allowed-updates-BD2bJyzD.js

---

Update Result: ERROR
Root: /home/emanu/.local/lib/node_modules/openclaw
Reason: openclaw doctor
Before: 2026.4.15
After: 2026.4.20

---

{
  "dependencies": {
    "grammy": "^1.42.0",
    "@grammyjs/runner": "^2.0.3",
    "@grammyjs/transformer-throttler": "^1.2.1"
  }
}

---

cd ~/.local/lib/node_modules/openclaw
npm install grammy@1.42.0 @grammyjs/runner@2.0.3 @grammyjs/transformer-throttler@1.2.1 --no-save --omit=dev --legacy-peer-deps
RAW_BUFFERClick to expand / collapse

Summary

openclaw update upgrades successfully to 2026.4.20, but the post-update openclaw doctor check fails because the installed global package cannot resolve grammy from the bundled Telegram extension.

Environment

  • Install method: global npm package in ~/.local/lib/node_modules/openclaw
  • OpenClaw before update: 2026.4.15
  • OpenClaw after update attempt: 2026.4.20
  • Node: v24.14.0
  • npm: 11.9.0
  • OS: Linux x64 (6.8.0-107-generic)

Reproduction

  1. Start from a working global install on 2026.4.15
  2. Run: 
    openclaw update
  3. Observe update output

Actual result

The package updates, but the final doctor step fails with:

Error: Cannot find module 'grammy'
Require stack:
- /home/emanu/.local/lib/node_modules/openclaw/dist/extensions/telegram/allowed-updates-BD2bJyzD.js

And openclaw update reports:

Update Result: ERROR
Root: /home/emanu/.local/lib/node_modules/openclaw
Reason: openclaw doctor
Before: 2026.4.15
After: 2026.4.20

Expected result

openclaw update should complete successfully, and openclaw doctor should be able to import bundled Telegram runtime code without manual dependency repair.

Diagnosis

The installed package contains Telegram extension files that import grammy, for example:

  • dist/extensions/telegram/allowed-updates-BD2bJyzD.js
  • dist/extensions/telegram/send-9ZV2dAUH.js
  • dist/extensions/telegram/bot-Dm2NPcQu.js

The bundled Telegram extension package metadata also declares:

{
  "dependencies": {
    "grammy": "^1.42.0",
    "@grammyjs/runner": "^2.0.3",
    "@grammyjs/transformer-throttler": "^1.2.1"
  }
}

But after openclaw update, the global install does not have grammy resolvable at runtime, and importing the Telegram extension fails immediately.

Verified workaround

Running this manually inside the installed global package repairs the install:

cd ~/.local/lib/node_modules/openclaw
npm install [email protected] @grammyjs/[email protected] @grammyjs/[email protected] --no-save --omit=dev --legacy-peer-deps

After that:

  • importing dist/extensions/telegram/allowed-updates-BD2bJyzD.js succeeds
  • openclaw doctor passes

However, rerunning openclaw update reinstalls the package and the same problem reappears.

Notes

This looks like a packaging/bundled-runtime-deps regression in 2026.4.20, not a local config issue.

extent analysis

TL;DR

The issue can be temporarily resolved by manually installing the required grammy dependencies in the global package directory after updating OpenClaw.

Guidance

  • Verify that the grammy package is not installed in the global package directory by checking the package.json file or running npm ls grammy in the ~/.local/lib/node_modules/openclaw directory.
  • Manually install the required grammy dependencies using the provided command: npm install [email protected] @grammyjs/[email protected] @grammyjs/[email protected] --no-save --omit=dev --legacy-peer-deps in the ~/.local/lib/node_modules/openclaw directory.
  • After manual installation, re-run openclaw doctor to verify that the issue is resolved.
  • Note that re-running openclaw update may reinstall the package and cause the issue to reappear, so a more permanent solution may be needed.

Example

No code snippet is necessary for this issue, as the problem is related to package dependencies and can be resolved using npm commands.

Notes

The issue appears to be a packaging regression in OpenClaw version 2026.4.20, and a more permanent solution may require changes to the OpenClaw packaging or dependency management.

Recommendation

Apply the provided workaround by manually installing the required grammy dependencies after updating OpenClaw, as this is the only known solution at this time. A more permanent solution may require waiting for an update to OpenClaw that addresses the packaging regression.

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…
#prompt template#agent execution#callback error#memory management#API rate limit

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix openclaw update fails on 2026.4.20 with missing grammy in Telegram bundled runtime [5 comments, 6 participants]