agent not responding to any session

[magic kettle]

I am trying to message my agent directly on the gateway dashboard and it just spins forever; I just fixed a bunch of stuff but now it isn't responding at all

[velvet crane]

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

[fair blaze]

First thing: what does openclaw --version show?

For “Dashboard chat spins forever”, the useful split is whether the Gateway is healthy but the agent run is stuck, or the Dashboard/WebSocket is losing the response stream. Please run these and paste the output/log errors:

openclaw --version
openclaw status --all
openclaw gateway status
openclaw doctor
openclaw models status
openclaw logs --follow

Then send one short test message in the Dashboard while openclaw logs --follow is running. The log line/error right after that is usually the answer.

Common things to look for:

• gateway not actually reachable: Connectivity probe not ok

[fair blaze]

• dashboard auth/device issue: pairing required, AUTH_TOKEN_MISMATCH, origin not allowed, unauthorized
• model/provider issue: missing auth, 401/429, model tool/schema errors, backend timeout
• stuck old run/session: try Dashboard Stop, or type /stop in that session, then send a tiny hi

Docs for the same triage ladder: https://docs.openclaw.ai/help/faq#first-60-seconds-if-something-is-broken and https://docs.openclaw.ai/help/troubleshooting

[magic kettle]

error Embedded agent failed before reply: All models failed (3): anthropic/claude-haiku-4-5: {"type":"error","error":{"type":"authentication_error","message":"invalid x-api-key"},"request_id":"req_011CbCbooDsru4Y6YrzuBVvW"} (auth) | anthropic/claude-opus-4-7: No available auth profile for anthropic (all in cooldown or unavailable). (auth) | anthropic/claude-sonnet-4-6: No available auth profile for anthropic (all in cooldown or unavailable). (auth) | No available auth profile for anthropic (all in cooldown or unavailable).

[fair blaze]

That error is model auth, not a session/channel problem.

invalid x-api-key means the Anthropic API key the Gateway is using is bad/revoked/mistyped. After that failure, OpenClaw has temporarily marked the other Anthropic profiles as unavailable/cooling down, so every fallback also fails.

Do this on the gateway host:

openclaw --version
openclaw models status --probe
openclaw models auth order get --provider anthropic

Then pick one fix path:

# API-key path: put a fresh Anthropic key where the gateway can read it

[fair blaze]

# e.g. in ~/.openclaw/.env as ANTHROPIC_API_KEY=sk-ant-...
openclaw models auth order clear --provider anthropic
openclaw gateway restart
openclaw models status --probe

or, if you want to use Claude CLI auth instead of an API key:

claude auth login
openclaw models auth login --provider anthropic --method cli --set-default
openclaw gateway restart
openclaw models status --probe

Important: if the Gateway is running under systemd/launchd, a key exported only in your current shell often won’t be visible to it. Put it in the Gateway’s env/config path, then restart the Gateway.

[fair blaze]

Docs: https://docs.openclaw.ai/providers/anthropic and https://docs.openclaw.ai/concepts/models#models-status

[magic kettle]

Got it, just had to update my anthropic api key. Thanks!

[fair blaze]

Glad that fixed it. 🎉

If this solved the thread, please right-click the solution message → Apps → ✅ Mark Solution so Answer Overflow indexes it for the next person who hits the same invalid x-api-key failure.