Agent not responding | Friends of the Crustacean 🦞🤝 | Page 1

warped loom Apr 16, 2026, 3:56 PM

#

My agent doesn't respond in the web interface or telegram.

hexed drumBOT Apr 16, 2026, 3:56 PM

#

mossy sailBOT Apr 16, 2026, 3:58 PM

#

If both the web UI and Telegram are silent, it’s usually the gateway/agent run failing, not just Telegram.

Please paste these first:

openclaw --version
openclaw status --all
openclaw gateway status
openclaw channels status --probe
openclaw models status

Then keep this running:

openclaw logs --follow

#

After that, send one test message from the web UI and one from Telegram, then paste the log lines that appear.

Fast checks while you do that:

Web UI shows disconnected (1008): pairing required

openclaw devices list
openclaw devices approve <requestId>

Web UI shows unauthorized / token mismatch
- In Control UI, go to Overview → Gateway Access
- Paste the current token from:
```
openclaw config get gateway.auth.token
```

#

Telegram DM is silent
```
openclaw pairing list telegram
```
If there’s a pending pairing, approve it, or check channels.telegram.dmPolicy / allowFrom.
Logs show Telegram network/fetch errors
- That usually means DNS/HTTPS/proxy trouble reaching api.telegram.org

Docs:

Paste the outputs and I’ll help narrow it down.

warped loom Apr 16, 2026, 4:00 PM

#

16:00:26+00:00 error gateway connect failed: GatewayClientRequestError: pairing required
16:00:26+00:00 error gateway connect failed: GatewayClientRequestError: pairing required

mossy sailBOT Apr 16, 2026, 4:01 PM

#

Yep, that narrows it down.

GatewayClientRequestError: pairing required means the gateway is refusing that client/device until it’s approved.

Run:

openclaw devices list
openclaw devices approve <requestId>

Then reconnect the web UI.

A couple notes:

If you’re connecting from Tailscale/LAN/another browser profile, this is expected.
If you retry with changed auth/details, the old request can get superseded, so re-run openclaw devices list and approve the latest request.

#

Loopback localhost (127.0.0.1 / localhost) should normally auto-approve. If you’re local and still seeing this, tell me, because that’s a useful clue.

After that, test Telegram again. If Telegram is still silent, next checks are:

openclaw pairing list telegram
openclaw channels status --probe
openclaw logs --follow

Docs:

If you want, paste the output of openclaw devices list and I’ll tell you exactly what to approve.

warped loom Apr 16, 2026, 4:20 PM

#

im local and seeing this

mossy sailBOT Apr 16, 2026, 4:21 PM

#

If you’re truly on local loopback, that’s weird. 127.0.0.1 / localhost should auto-approve the browser device.

So the usual gotchas are:

you opened the UI on a LAN IP, Tailscale IP/MagicDNS, or a reverse proxy
the UI has a cached non-loopback gateway URL
you’re using a different browser profile / custom dev UI

Please check these exactly:

openclaw gateway status --json
openclaw devices list

Then make sure you are opening:

#

http://127.0.0.1:18789/

and not http://<your-lan-ip>:18789/ or a proxy URL.

In the UI, check Overview → Gateway Access and make sure the gateway URL is loopback too, for example:

ws://127.0.0.1:18789

Important nuance: localhost still needs auth/token, but it should not require manual device pairing.

If openclaw devices list shows a pending request, approve it anyway for now:

#Agent not responding