openclaw - ✅(Solved) Fix [Bug]: Telegram plugin fails to load after upgrade to 2026.3.27 [1 pull requests, 3 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#56219Fetched 2026-04-08 01:43:26
View on GitHub
Comments
3
Participants
2
Timeline
10
Reactions
0
Timeline (top)
commented ×3labeled ×2referenced ×2closed ×1

Environment:

OpenClaw version: 2026.3.27 OS: Ubuntu (Linux 6.17.0) Node.js: v24.14.0 Error:

TypeError: (0 , _directoryRuntime.createInspectedDirectoryEntriesLister) is not a function Plugin source: /home/justin/openclaw/extensions/telegram/index.ts

Error Message

Error: Gateway starts → Telegram plugin fails to load with the error above Error: The error is thrown from directory-runtime.ts in the Telegram extension's call to createInspectedDirectoryEntriesLister — this function does not exist in the current SDK

Root Cause

Environment:

OpenClaw version: 2026.3.27 OS: Ubuntu (Linux 6.17.0) Node.js: v24.14.0 Error:

TypeError: (0 , _directoryRuntime.createInspectedDirectoryEntriesLister) is not a function Plugin source: /home/justin/openclaw/extensions/telegram/index.ts

Fix Action

Fixed

PR fix notes

PR #56302: fix(telegram): add devDependencies and peerDependencies for openclaw (#56219)

Description (problem / solution / changelog)

Fixes #56219

Problem

After upgrading to OpenClaw 2026.3.27, Telegram plugin fails to load with error:

TypeError: (0 , _directoryRuntime.createInspectedDirectoryEntriesLister) is not a function
Plugin source: /home/justin/openclaw/extensions/telegram/index.ts

Root Cause

The telegram plugin was missing devDependencies and peerDependencies declarations for openclaw.

According to repo guidelines:

Plugins: put openclaw in devDependencies or peerDependencies instead (runtime resolves openclaw/plugin-sdk via jiti alias).

Without these declarations, the plugin cannot properly resolve openclaw/plugin-sdk/* imports at runtime when installed via npm.

Comparison:

  • ✅ discord plugin has both devDependencies and peerDependencies
  • ❌ telegram plugin was missing both (removed in v2026.2.24)

Solution

Add devDependencies and peerDependencies to telegram plugin's package.json, matching the discord plugin configuration:

{
  "devDependencies": {
    "openclaw": "workspace:*"
  },
  "peerDependencies": {
    "openclaw": ">=2026.3.27"
  },
  "peerDependenciesMeta": {
    "openclaw": {
      "optional": true
    }
  }
}

Impact

  • ✅ Fixes #56219 - Telegram plugin load failure
  • ✅ Ensures proper runtime resolution of openclaw/plugin-sdk/* imports
  • ✅ Aligns telegram plugin with repo guidelines and other plugins (discord)
  • ✅ No breaking changes

Testing

  • Type check: ✅ Passed
  • Lint: ✅ Passed

Files Changed

  • extensions/telegram/package.json (+11 lines)

Changed files

  • extensions/telegram/package.json (modified, +11/-0)
RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

Environment:

OpenClaw version: 2026.3.27 OS: Ubuntu (Linux 6.17.0) Node.js: v24.14.0 Error:

TypeError: (0 , _directoryRuntime.createInspectedDirectoryEntriesLister) is not a function Plugin source: /home/justin/openclaw/extensions/telegram/index.ts

Steps to reproduce

Steps to reproduce:

Upgrade from previous version to 2026.3.27 Telegram channel is configured in openclaw.json Gateway starts → Telegram plugin fails to load with the error above

Expected behavior

Expected behavior: Telegram plugin should load normally, allowing bot to receive/respond to messages.

Actual behavior

Error:

TypeError: (0 , _directoryRuntime.createInspectedDirectoryEntriesLister) is not a function Plugin source: /home/justin/openclaw/extensions/telegram/index.ts

OpenClaw version

2026.3.27

Operating system

Ubuntu Desktop 25

Install method

npm globla

Model

minimax2.7

Provider / routing chain

openclaw-minimax

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

Additional context:

QQBot works fine after the same upgrade Telegram plugin worked before upgrade Reloading config or restarting gateway does not fix the issue The error is thrown from directory-runtime.ts in the Telegram extension's call to createInspectedDirectoryEntriesLister — this function does not exist in the current SDK

extent analysis

Fix Plan

The fix involves updating the Telegram plugin to use the correct function from the directoryRuntime module.

  • Check the directoryRuntime module documentation for the correct function to use instead of createInspectedDirectoryEntriesLister.
  • Update the index.ts file in the Telegram plugin to use the new function.

Example code:

// Before
import { createInspectedDirectoryEntriesLister } from './directoryRuntime';
const lister = createInspectedDirectoryEntriesLister();

// After
import { createDirectoryEntriesLister } from './directoryRuntime';
const lister = createDirectoryEntriesLister();
  • If the createDirectoryEntriesLister function does not exist, you may need to create a custom implementation or use a different approach to achieve the same functionality.

Verification

To verify the fix, restart the gateway and check if the Telegram plugin loads successfully. You can also add logging statements to the index.ts file to confirm that the new function is being called correctly.

Extra Tips

  • Make sure to update the directoryRuntime module to the latest version to ensure you have the latest functions and features.
  • If you are using a custom implementation, consider contributing it back to the OpenClaw project to help others who may be facing the same 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…

FAQ

Expected behavior

Expected behavior: Telegram plugin should load normally, allowing bot to receive/respond to messages.

Still need to ship something?

×6

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

Back to top recommendations

TRENDING