Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: Empty response payloads=0 on all models — fresh install [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#81527•Fetched 2026-05-14 03:31:12
View on GitHub
Comments
1
Participants
2
Timeline
3
Reactions
2
Author
whitb1whitb1
Participants
clawsweeper[bot]clawsweeper[bot]whitb1whitb1
Timeline (top)
labeled ×2commented ×1

Fresh install, full reset. API key valid (confirmed via direct curl — returns pong). Gateway starts clean, auth resolves, but every chat message returns empty response with payloads=0.

Error: "empty response detected... stopReason=stop payloads=0" Error hash: sha256:9c64499aecc5

Tested on both claude-haiku-4-5-20251001 and claude-sonnet-4-5-20250929. Same result on both. Web UI shows message sent but no response ever appears.

Version: 2026.5.7 OS: macOS 26.3

Error Message

Error: "empty response detected... stopReason=stop payloads=0" Error hash: sha256:9c64499aecc5 Error hash: sha256:9c64499aecc5 empty response retries exhausted: attempts=1/1 — surfacing incomplete-turn error incomplete turn detected: stopReason=stop payloads=0 — surfacing error to user

Root Cause

Fresh install, full reset. API key valid (confirmed via direct curl — returns pong). Gateway starts clean, auth resolves, but every chat message returns empty response with payloads=0.

Error: "empty response detected... stopReason=stop payloads=0" Error hash: sha256:9c64499aecc5

Tested on both claude-haiku-4-5-20251001 and claude-sonnet-4-5-20250929. Same result on both. Web UI shows message sent but no response ever appears.

Version: 2026.5.7 OS: macOS 26.3

Fix Action

Fix / Workaround

Affected: All users configuring OpenClaw with direct Anthropic API key on fresh install Severity: Critical — blocks all agent functionality, no workaround found Frequency: Always — 100% reproducible on every message sent Consequence: Failed onboarding, agent completely non-functional

Code Example

empty response detected: provider=anthropic/claude-haiku-4-5-20251001 — retrying 1/1 with visible-answer continuation
empty response retries exhausted: attempts=1/1 — surfacing incomplete-turn error
incomplete turn detected: stopReason=stop payloads=0 — surfacing error to user
errorHash: sha256:9c64499aecc5
RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

Fresh install, full reset. API key valid (confirmed via direct curl — returns pong). Gateway starts clean, auth resolves, but every chat message returns empty response with payloads=0.

Error: "empty response detected... stopReason=stop payloads=0" Error hash: sha256:9c64499aecc5

Tested on both claude-haiku-4-5-20251001 and claude-sonnet-4-5-20250929. Same result on both. Web UI shows message sent but no response ever appears.

Version: 2026.5.7 OS: macOS 26.3

Steps to reproduce

  1. Fresh install of OpenClaw 2026.5.7 on macOS
  2. Run openclaw setup --wizard, configure Anthropic API key
  3. Start gateway, open Web UI at http://127.0.0.1:18789
  4. Send any message
  5. Observe no response returned

Expected behavior

Agent responds to messages via Web UI. API key is valid — direct curl test returns successful response from Anthropic.

Actual behavior

No response returned in Web UI. Gateway log shows: "empty response detected... stopReason=stop payloads=0" Error hash: sha256:9c64499aecc5 Affects both claude-haiku-4-5-20251001 and claude-sonnet-4-5-20250929

OpenClaw version

2026.5.7 (eeef486)

Operating system

macOS 26.3.1

Install method

brew (homebrew)

Model

anthropic/claude-haiku-4-5-20251001 and anthropic/claude-sonnet-4-5-20250929

Provider / routing chain

openclaw -> anthropic (direct API key)

Additional provider/model setup details

Direct Anthropic API key configured via openclaw setup --wizard. No proxy or gateway in between. API key confirmed valid via direct curl test returning successful response.

Logs, screenshots, and evidence

empty response detected: provider=anthropic/claude-haiku-4-5-20251001 — retrying 1/1 with visible-answer continuation
empty response retries exhausted: attempts=1/1 — surfacing incomplete-turn error
incomplete turn detected: stopReason=stop payloads=0 — surfacing error to user
errorHash: sha256:9c64499aecc5

Impact and severity

Affected: All users configuring OpenClaw with direct Anthropic API key on fresh install Severity: Critical — blocks all agent functionality, no workaround found Frequency: Always — 100% reproducible on every message sent Consequence: Failed onboarding, agent completely non-functional

Additional information

No response

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

Agent responds to messages via Web UI. API key is valid — direct curl test returns successful response from Anthropic.

#api#file not found#serialization error#model compatibility#GPU setup

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING