Issue Station
Sign In
Tools hereToolbox

openclaw - ✅(Solved) Fix Upgrade from 3.24 to 3.31 silently breaks Telegram — channel moved to plugin but existing config not migrated [1 pull requests, 1 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#58848•Fetched 2026-04-08 02:31:55
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Author
qingcaohuangqingcaohuang
Participants
qingcaohuangqingcaohuang
Timeline (top)
closed ×1cross-referenced ×1locked ×1

Error Message

After upgrading OpenClaw from 2026.3.24 to 2026.3.31, Telegram stops working silently. No error messages, no warnings in logs — Telegram channel simply does not initialize on Gateway startup. 5. Telegram no longer initializes — no error in logs, no channel in openclaw channels status

  • Or: openclaw doctor should warn that channels.telegram exists but the telegram plugin is disabled

Root Cause

In 3.31, Telegram was moved from a built-in channel to a plugin (plugins.entries.telegram). However, existing installations that had channels.telegram configured in 3.24 do not get plugins.entries.telegram added automatically during upgrade. Since the plugin defaults to disabled, Telegram silently stops working.

Fix Action

Workaround

Add to openclaw.json:

{
  "plugins": {
    "entries": {
      "telegram": { "enabled": true }
    },
    "allow": ["telegram"]
  }
}

PR fix notes

PR #58873: fix: preserve bundled channel plugin compat

Description (problem / solution / changelog)

Summary

  • keep bundled channel plugins loadable when legacy channels.<id>.enabled=true config is used under a restrictive plugins.allow
  • add doctor warnings for real channel-plugin blockers and suppress misleading setup guidance when the plugin is explicitly blocked
  • add regression coverage for loader, enable-state, and doctor flows

Fixes #58848

Changed files

  • CHANGELOG.md (modified, +1/-0)
  • src/commands/doctor-config-flow.test.ts (modified, +50/-0)
  • src/commands/doctor/shared/channel-plugin-blockers.ts (added, +96/-0)
  • src/commands/doctor/shared/preview-warnings.test.ts (modified, +69/-0)
  • src/commands/doctor/shared/preview-warnings.ts (modified, +13/-1)
  • src/plugins/config-state.test.ts (modified, +26/-0)
  • src/plugins/config-state.ts (modified, +2/-1)
  • src/plugins/loader.test.ts (modified, +16/-0)

Code Example

{
  "plugins": {
    "entries": {
      "telegram": { "enabled": true }
    },
    "allow": ["telegram"]
  }
}
RAW_BUFFERClick to expand / collapse

Bug Description

After upgrading OpenClaw from 2026.3.24 to 2026.3.31, Telegram stops working silently. No error messages, no warnings in logs — Telegram channel simply does not initialize on Gateway startup.

Root Cause

In 3.31, Telegram was moved from a built-in channel to a plugin (plugins.entries.telegram). However, existing installations that had channels.telegram configured in 3.24 do not get plugins.entries.telegram added automatically during upgrade. Since the plugin defaults to disabled, Telegram silently stops working.

Steps to Reproduce

  1. Install OpenClaw 2026.3.24
  2. Configure channels.telegram with a valid bot token — Telegram works fine
  3. Upgrade to 2026.3.31 via npm install -g openclaw@latest
  4. Restart Gateway
  5. Telegram no longer initializes — no error in logs, no channel in openclaw channels status

Expected Behavior

  • Either: auto-migrate existing channels.telegram config to also enable plugins.entries.telegram
  • Or: openclaw doctor should warn that channels.telegram exists but the telegram plugin is disabled
  • Or: Gateway startup should log a warning like "channels.telegram configured but telegram plugin is disabled"

Actual Behavior

  • Gateway starts without any Telegram-related log output
  • openclaw channels status shows no channels
  • openclaw doctor says "Telegram is in first-time setup mode" (misleading)
  • openclaw plugins list shows telegram as disabled (the actual clue)

Workaround

Add to openclaw.json:

{
  "plugins": {
    "entries": {
      "telegram": { "enabled": true }
    },
    "allow": ["telegram"]
  }
}

Environment

  • OS: Linux 6.8.0-106-generic (x64)
  • Node: v22.22.0
  • OpenClaw: upgraded from 2026.3.24 → 2026.3.31

extent analysis

TL;DR

Enable the Telegram plugin by adding the necessary configuration to openclaw.json to fix the silent failure of Telegram initialization after upgrading OpenClaw.

Guidance

  • Verify that the plugins.entries.telegram configuration is missing or set to disabled in openclaw.json after the upgrade.
  • Add the workaround configuration to openclaw.json as specified to enable the Telegram plugin.
  • Check the openclaw plugins list output to confirm that the Telegram plugin is now enabled.
  • Restart the Gateway after applying the configuration change to ensure Telegram initializes correctly.

Example

The necessary configuration to enable the Telegram plugin is:

{
  "plugins": {
    "entries": {
      "telegram": { "enabled": true }
    },
    "allow": ["telegram"]
  }
}

This should be added to the existing openclaw.json file.

Notes

This fix assumes that the issue is solely due to the missing or disabled Telegram plugin configuration after the upgrade. If other issues are present, additional troubleshooting may be necessary.

Recommendation

Apply the workaround by adding the necessary configuration to openclaw.json to enable the Telegram plugin, as this is a direct fix for the identified root cause.

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…
#installation#SSR setup#ISR setup#authentication setup#request error

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 - ✅(Solved) Fix Upgrade from 3.24 to 3.31 silently breaks Telegram — channel moved to plugin but existing config not migrated [1 pull requests, 1 participants]