OpenClaw `status` vs `gateway status`: 5-Minute Debug Flow for “Online but No Reply” (2026)

When you hit “bot is online, but no reply,” the first mistake is often diagnostic:

• You only run openclaw status and assume Gateway is healthy
• Or you only run openclaw gateway status and assume channels are healthy

These commands operate at different layers. Mixing them causes false conclusions.

One-line answer

• openclaw gateway status: validates the Gateway service layer (runtime + probe)
• openclaw status: validates the channel/session layer (Telegram/Discord/Slack/Signal health snapshot)

Check gateway first, then channels.

1) Role split: quick comparison

Verify directly from local CLI help:

openclaw status --help
openclaw gateway status --help

Pending confirmation: output field names can vary by version; commands in this guide were verified against local OpenClaw 2026.3.3 help text.

2) 5-minute troubleshooting flow (copy/paste)

Step 1: Is Gateway alive? (30s)

openclaw gateway status

If suspicious, run deep scan:

openclaw gateway status --deep

If not healthy, recover first:

openclaw gateway restart
openclaw gateway status

Decision rule:

• Gateway unhealthy → fix gateway first (don’t start with Telegram token edits)
• Gateway healthy → move to channel checks

Step 2: Are channels healthy? (1-2 min)

openclaw status
openclaw status --deep --timeout 10000

Need a pasteable full snapshot?

openclaw status --all

Decision rule:

• Gateway healthy + channel unhealthy → channel config/permission/network issue
• Gateway healthy + channel healthy but still no replies → inspect runtime logs

Step 3: Confirm message path in logs

openclaw logs --follow

Send a test message from your chat client while tailing logs, then verify inbound/routing/outbound events appear.

3) Why misdiagnosis happens (real patterns)

Pattern A: openclaw status looks “mostly fine,” but gateway just crashed

• Channel snapshot ≠ gateway process stability
• Run openclaw gateway status --deep to confirm service health

Pattern B: openclaw gateway status is healthy, but Telegram still silent

• Service alive ≠ channel path valid
• Pivot to openclaw status --deep and channel-specific auth/conflict checks

Pattern C: Sharing only one screenshot

Use this minimum evidence pack for fast triage:

openclaw gateway status --deep
openclaw status --all
openclaw logs --follow

4) Verifiable checklist

• openclaw gateway status confirms gateway service state
• openclaw status --deep confirms channel probe results
• openclaw status --all provides a shareable diagnosis snapshot
• openclaw logs --follow confirms real-time message path events

If all four are complete, you can confidently decide whether to fix the gateway layer or the channel layer.

Related guides (internal links)

• OpenClaw Telegram Troubleshooting Guide
• OpenClaw Gateway Start Failed? 2026 Fix Checklist
• OpenClaw Logs Debug Guide: From Error to Root Cause