Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: Telegram group /status silently no-replies on 2026.4.27 while normal messages work [2 comments, 3 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#74698•Fetched 2026-04-30 06:21:08
View on GitHub
Comments
2
Participants
3
Timeline
5
Reactions
3
Author
tess020126-cmyktess020126-cmyk
Participants
byungskersbyungskersclawsweeper[bot]clawsweeper[bot]tess020126-cmyktess020126-cmyk
Timeline (top)
commented ×2cross-referenced ×1mentioned ×1subscribed ×1
RAW_BUFFERClick to expand / collapse

Bug

Telegram group slash commands such as /status no longer produce a response in group sessions on OpenClaw 2026.4.27, while normal group messages still route to the agent successfully.

Environment

  • OpenClaw: 2026.4.27
  • OS: macOS 15.7.3 (x64)
  • Node: 25.5.0
  • Channel: Telegram
  • Gateway: local loopback, reachable
  • Telegram channel status: OK
  • Setup: multiple Telegram group sessions bound to OpenClaw agents/advisors

Reproduction

  1. In a configured Telegram group session, send /status.
  2. Observe no status reply is sent.
  3. Send a normal text message in the same group.
  4. Observe the agent/group session does receive and respond to normal text.
  5. Repeat in another configured Telegram group, same result.

Confirmed affected locally:

  • One group agent: normal text Test produced a successful agent reply.
  • A second configured group also reproduced /status no-response.

Expected behavior

/status should be handled by the Gateway and send a status card/reply back to the Telegram group session, as it previously did.

Actual behavior

/status appears to be silently swallowed/no visible response in Telegram groups. Normal non-slash text still works.

Local evidence

After a gateway restart to recover the affected group runner:

  • openclaw status --deep reports Gateway reachable and Telegram OK.
  • Affected group session exists and is healthy:
    • agent group session present
    • model: openai-codex/gpt-5.5
    • tokens: about 22k / 272k
  • Transcript exists and contains normal text turns:
    • user Test -> assistant sent a successful reply
    • user Good -> no visible reply expected
  • Later /status attempts did not create the expected visible Gateway status reply.

Related prior issues

This resembles, but may not be identical to, older closed Telegram group slash-command issues:

  • #28201 Slash commands silently ignored in Telegram forum group topics
  • #29135 Telegram: slash commands return 'not authorized' in forum topic chats
  • #30234 Telegram native command auth in groups checks DM allowlist instead of groupAllowFrom
  • #28216 Telegram native command handler ignores commands.allowFrom in group chats
  • #48707 /stop command does not target topic session in Telegram forum groups
  • #57738 Telegram group messages not reaching gateway (long polling) — DMs work fine

This repro is on latest 2026.4.27 and affects at least two configured Telegram group sessions while normal messages continue working.

extent analysis

TL;DR

The issue with Telegram group slash commands not producing a response in OpenClaw 2026.4.27 may be related to changes in handling slash commands, and verifying the configuration of the Gateway and Telegram channel settings could help resolve the issue.

Guidance

  • Review the related prior issues (#28201, #29135, #30234, #28216, #48707, #57738) to see if any of the fixes or workarounds apply to the current situation.
  • Check the Gateway configuration to ensure that slash commands are properly handled and routed to the correct agent/advisor.
  • Verify that the Telegram channel settings, such as the allowlist, are correctly configured to allow slash commands from the group sessions.
  • Test slash commands in a different environment or setup to see if the issue is specific to the current configuration.

Example

No code snippet is provided as the issue does not contain enough information to create a specific example.

Notes

The issue may be related to changes in the handling of slash commands in OpenClaw 2026.4.27, and further investigation is needed to determine the root cause.

Recommendation

Apply workaround: Review and adjust the Gateway and Telegram channel settings to ensure proper handling of slash commands, as the issue may be related to configuration rather than a version-specific bug.

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

/status should be handled by the Gateway and send a status card/reply back to the Telegram group session, as it previously did.

#GPU compatibility#latency issue#model loading#dependency error#configuration 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 - 💡(How to fix) Fix [Bug]: Telegram group /status silently no-replies on 2026.4.27 while normal messages work [2 comments, 3 participants]