Bug: Tool result history corruption causing session lock (v2026.2.3-1)
✅Solved
Bug: Tool result history corruption causing session lock (v2026.2.3-1)
Environment:
• OpenClaw v2026.2.3-1
• Windows 11, Node v24.13.0
• Model: claude-opus-4-5
What happened:
During a long task (distilling a PineScript reference doc), the session became stuck. Every subsequent message returned:
LLM request rejected: messages.82.content.1: unexpected tool_use_id found in tool_result blocks: toolu_012DdgPHZPoefW3W6vqvDc4k. Each tool_result block must have a corresponding tool_use block in the previous message.
Impact:
Session completely unrecoverable — required /new or /reset to clear corrupted history.
Suspected cause:
Tool call/result pairing got deserialized incorrectly, possibly from a timeout, interrupted response, or race condition during message history serialization.
Note: This is separate from the cron regression also reported today on v2026.2.3-1.
Environment:
• OpenClaw v2026.2.3-1
• Windows 11, Node v24.13.0
• Model: claude-opus-4-5
What happened:
During a long task (distilling a PineScript reference doc), the session became stuck. Every subsequent message returned:
LLM request rejected: messages.82.content.1: unexpected tool_use_id found in tool_result blocks: toolu_012DdgPHZPoefW3W6vqvDc4k. Each tool_result block must have a corresponding tool_use block in the previous message.
Impact:
Session completely unrecoverable — required /new or /reset to clear corrupted history.
Suspected cause:
Tool call/result pairing got deserialized incorrectly, possibly from a timeout, interrupted response, or race condition during message history serialization.
Note: This is separate from the cron regression also reported today on v2026.2.3-1.
Solution
That error is coming from the Anthropic Messages API being very strict: every
What would help to debug / turn this into a fix:
1) Session file (best signal)
- Grab the session JSON from:
-
- (Default state dir is usually
- Specifically we want the area around
2) Logs around the moment it got corrupted
- Please paste:
-
- and ~50–200 lines from
3) Any interruption signals
- Did anything like this happen right before it “locked”?
tool_resulttool_usetool_resulttool_useWhat would help to debug / turn this into a fix:
1) Session file (best signal)
- Grab the session JSON from:
-
$OPENCLAW_STATE_DIR/agents/<agentId>/sessions/…- (Default state dir is usually
~/.openclaw%USERPROFILE%\.openclaw- Specifically we want the area around
messages[82]toolu_...2) Logs around the moment it got corrupted
- Please paste:
-
openclaw status --all- and ~50–200 lines from
openclaw logs --limit 2003) Any interruption signals
- Did anything like this happen right before it “locked”?
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
83,815Members
Resources
Was this page helpful?
