#Empty responses from OpenRouter — any ideas?

1 messages · Page 1 of 1 (latest)

glossy basalt
#

Hey — first time setting up OpenClaw today and stuck. Hoping someone can help 🙏

Running 2026.4.15 on macOS with OpenRouter (Claude Sonnet 4.6). API key works fine on the OpenRouter site. But when I send a message in the web dashboard or Telegram, I just get "Agent couldn't generate a response" — nothing actually comes back from the AI.
I've tried re-running onboard, the doctor command, and even downgrading to 2026.4.12 — same thing.
The gateway logs are spamming "pairing required" errors constantly, and when I try openclaw devices approve --latest it keeps saying "unknown requestId" no matter how fast I run it.

Has anyone got this setup working? Or know what I'm missing?

still lionBOT
zenith depotBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

still lionBOT
robust heronBOT
#

Yep, there’s one confirmed gotcha here, and probably one second issue.

1) openclaw devices approve --latest does not approve anymore
In current docs/CLI, --latest only previews the newest pending request. You need the exact request ID:

openclaw devices list
openclaw devices approve REQ_ID_HERE

Also, if the browser/device keeps reconnecting, the old pending request gets superseded and a new requestId is created, which explains the unknown requestId loop. So:

  • keep the failing dashboard/browser open
  • run openclaw devices list
  • copy the newest requestId
  • immediately run openclaw devices approve THAT_EXACT_ID
#

Docs: https://docs.openclaw.ai/cli/devices

2) If you’re on the same Mac, use http://127.0.0.1:18789/
Loopback browser connects should auto-approve. If you’re opening the dashboard via LAN/Tailscale/non-loopback URL, pairing is expected.

Dashboard auth/pairing docs: https://docs.openclaw.ai/web/dashboard#if-you-see-unauthorized-1008

3) The Telegram “Agent couldn’t generate a response” part may be separate
Since Telegram is failing too, I’d also check model/auth resolution, not just pairing.

Please run and paste:

openclaw status --all
openclaw models status --probe
openclaw devices list --json