#Bot not responding

1 messages · Page 1 of 1 (latest)

limber violet
#

Why did my bot not respond "17:32:39 info gateway/ws {"subsystem":"gateway/ws"} webchat connected conn=4f44b803-41a7-4347-ad5c-6189802537a6 remote=127.0.0.1 client=openclaw-control-ui webchat vdev
17:32:39 info gateway/ws {"subsystem":"gateway/ws"} ⇄ res ✓ chat.history 53ms conn=4f44b803…37a6 id=bfd2311d…b912
17:32:39 info gateway/ws {"subsystem":"gateway/ws"} ⇄ res ✓ node.list 120ms conn=4f44b803…37a6 id=e9e919d0…4a7b
17:32:39 info gateway/ws {"subsystem":"gateway/ws"} ⇄ res ✓ device.pair.list 175ms conn=4f44b803…37a6 id=4c8cb9c8…8f64
17:34:"

timid steppeBOT
# limber violet Why did my bot not respond "17:32:39 info gateway/ws {"subsystem":"gateway/ws"} ...

Those lines don’t show the bot “deciding not to respond” — they only show the Control UI WebSocket connecting and doing basic RPCs:

  • webchat connected … client=openclaw-control-ui = the dashboard/UI connected to the Gateway
  • chat.history, node.list, device.pair.list = the UI fetching data
  • there’s no log line showing an incoming chat message, an agent run, a model call, or an outbound reply

So the missing reply is almost certainly after this snippet (or the message never reached the Gateway at all).

What to paste next (quick triage):

openclaw --version
openclaw status --all
openclaw models status
openclaw channels status

Then reproduce it with live logs: