Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: `openclaw status` doesn't show channel list [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#73518•Fetched 2026-04-29 06:18:53
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
duping812duping812
Participants
clawsweeper[bot]clawsweeper[bot]duping812duping812
Timeline (top)
labeled ×2closed ×1commented ×1

openclaw status command hangs without displaying channel list. Gateway returns Capability: read-only in the status output, and the command never completes.

Root Cause

openclaw status command hangs without displaying channel list. Gateway returns Capability: read-only in the status output, and the command never completes.

Code Example

openclaw channels status --probe

---

Feishu default: enabled, configured, running, works
openclaw-weixin: enabled, configured, running, in:2m ago

---

Gateway: bind=loopback (127.0.0.1), port=18789
Runtime: running (pid 1857, state active, sub running)
Capability: read-only

---
RAW_BUFFERClick to expand / collapse

Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

openclaw status command hangs without displaying channel list. Gateway returns Capability: read-only in the status output, and the command never completes.

Steps to reproduce

  1. Run openclaw status
  2. Command hangs indefinitely (must be killed after timeout)
  3. No channel list is displayed

Alternative (works correctly):

openclaw channels status --probe

Output correctly shows:

Feishu default: enabled, configured, running, works
openclaw-weixin: enabled, configured, running, in:2m ago

Expected behavior

openclaw status should display all configured channels, similar to channels status --probe.

Actual behavior

Gateway Status Output:

Gateway: bind=loopback (127.0.0.1), port=18789
Runtime: running (pid 1857, state active, sub running)
Capability: read-only

Additional Context:

  • openclaw channels list also returns empty for chat channels
  • openclaw channels status --probe works fine and shows all channels
  • The issue may be related to the read-only capability flag blocking the status query

OpenClaw version

OpenClaw 2026.4.26 (be8c246)

Operating system

Windows 11 WSL2

Install method

npm global

Model

minimax

Provider / routing chain

openclaw -> minimax

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

extent analysis

TL;DR

The openclaw status command may be hanging due to the read-only capability flag, and using the --probe option with openclaw channels status works as a potential workaround.

Guidance

  • Investigate the cause of the read-only capability flag in the Gateway Status Output, as it may be blocking the status query.
  • Compare the implementation of openclaw status and openclaw channels status --probe to identify differences that could be contributing to the issue.
  • Verify that the openclaw channels list command also returns empty results for chat channels, as this may be related to the same underlying issue.
  • Consider modifying the openclaw status command to use a similar approach as openclaw channels status --probe if possible.

Example

No code example is provided as the issue does not contain sufficient information about the implementation details.

Notes

The issue may be specific to the OpenClaw version (2026.4.26) or the operating system (Windows 11 WSL2), so testing with different versions or environments may be necessary.

Recommendation

Apply workaround: use openclaw channels status --probe instead of openclaw status until the root cause of the read-only capability flag is resolved.

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

openclaw status should display all configured channels, similar to channels status --probe.

#SSR setup#ISR setup#authentication setup#request error#file not found

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 [Bug]: `openclaw status` doesn't show channel list [1 comments, 2 participants]