Exact symptom guide · Independent guidance

Fix OpenClaw “LLM request failed”

“LLM request failed” is a symptom, not one root cause. Preserve the provider/model reference and redacted error category, then check model visibility, auth profile state, provider reachability, quota/rate limits, and a narrow model probe before changing fallbacks or the whole config.

Current snapshotUpdated 2026-08-24Official docs main snapshot · OpenClaw 2026.8.1
01

Evidence-first sequence

  1. 1

    Confirm the selected model

    Record the exact provider/model and fallback list.

    openclaw models status --json
    openclaw models list
  2. 2

    Inspect auth state

    Do not print the underlying token or API key.

    openclaw models auth list --json
  3. 3

    Run doctor

    Look for provider, SecretRef, routing, plugin, and config findings.

    openclaw doctor --json
  4. 4

    Test the narrowest path

    Use a small direct provider/local-model probe before a full tool-rich agent turn.

02

Interpret the category, not just the message

  • 401/403: credential, account, method, or permission mismatch.
  • 404/unknown model: wrong provider/model reference or unavailable catalog entry.
  • 429/quota: rate, balance, concurrency, or account-plan limit.
  • Timeout/network: DNS, proxy, TLS, firewall, endpoint, or provider availability.
  • Local model plain-text success but agent failure: tool calling, context, or agent-capability mismatch.
  • Fallback success: useful availability evidence, but the primary failure still needs an explicit decision.

Primary sources

Verify against the owner.

Content snapshot follows official docs main at the recorded commit; the current package metadata reported 2026.8.1 when verified. Your installed release and live CLI schema remain authoritative.