Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix openclaw status does not show active Telegram channel because status command does not load plugin registry [1 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#73824•Fetched 2026-04-29 06:14:37
View on GitHub
Comments
1
Participants
2
Timeline
2
Reactions
0
Author
liorb-mountappsliorb-mountapps
Participants
clawsweeper[bot]clawsweeper[bot]liorb-mountappsliorb-mountapps
Timeline (top)
closed ×1commented ×1

Code Example

channels: {
  telegram: {
    enabled: true,
    accounts: {
      agent1: {
        enabled: true,
        dmPolicy: allowlist
      }
    }
  }
}

---

[gateway] http server listening (1 plugin: telegram; 2.2s)
[telegram] [agent1] starting provider

---

[ws] res ✓ channels.status 65ms

---

const PLUGIN_REQUIRED_COMMANDS = new Set([message, channels, directory]);
RAW_BUFFERClick to expand / collapse

OpenClaw version: 2026.4.26

Observed:

The agent responds on Telegram, but openclaw status shows an empty Channels table.

Live config has Telegram enabled:

channels: {
  telegram: {
    enabled: true,
    accounts: {
      agent1: {
        enabled: true,
        dmPolicy: allowlist
      }
    }
  }
}

Gateway logs show Telegram is loaded and running:

[gateway] http server listening (1 plugin: telegram; 2.2s)
[telegram] [agent1] starting provider

Gateway also answers channel status calls:

[ws] res ✓ channels.status 65ms

Expected:

openclaw status should show Telegram in the Channels table when Telegram is configured and active.

Likely cause:

openclaw status builds its channels table from listChannelPlugins(), which depends on the active plugin registry.

But CLI pre-action only loads plugins for these commands:

const PLUGIN_REQUIRED_COMMANDS = new Set([message, channels, directory]);

status is not included, so the status command can render an empty Channels table even though the gateway has Telegram loaded.

extent analysis

TL;DR

The openclaw status command may not show Telegram in the Channels table because the CLI does not load plugins for the status command.

Guidance

  • The issue is likely caused by the status command not loading plugins, which is required to populate the Channels table.
  • To verify, check the PLUGIN_REQUIRED_COMMANDS set in the code to confirm that status is not included.
  • Consider modifying the PLUGIN_REQUIRED_COMMANDS set to include status to ensure plugins are loaded for this command.
  • Alternatively, investigate if there's an existing issue or feature request to add status to the PLUGIN_REQUIRED_COMMANDS set.

Example

No code snippet is provided as it's not necessary to illustrate the solution.

Notes

This solution assumes that the PLUGIN_REQUIRED_COMMANDS set is the root cause of the issue. If this is not the case, further investigation may be required.

Recommendation

Apply workaround: Modify the PLUGIN_REQUIRED_COMMANDS set to include status to ensure plugins are loaded for this command. This is a targeted fix that addresses the likely cause of the 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…
#parallel task#integration issue#index setup#retrieval issue#search optimization

Still need to ship something?

×6

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

Back to top recommendations

TRENDING