`tool_use` ids were found without `tool_result` blocks immediately after

[beaugast]

Session ID: v2:b6f9a229-8460-4e94-8f4d-d40c4d8fb5c7
Session Schema: v2.0
Pro User ID: ****iLCm

Issue Description (required)

Error: 400 litellm.BadRequestError: AnthropicException - b'{"type":"error","error":{"type":"invalid_request_error","message":"messages.13: tool_use ids were found without tool_result blocks immediately after: toolu_01SXeki1uX2AGU9TSaYsLZQn. Each tool_use block must have a corresponding tool_result block in the next message."},"request_id":"req_011CZNQd5i5ZUy5sABKmCaWA"}'No fallback model group found for original model_group=anthropic/claude-opus-4-6.

Expected Behavior (required)

Not fail.

Actual Behavior (required)

Failed.

System Information

• Dyad Version: 0.40.0
• Platform: win32
• Architecture: x64
• Node Version: v22.14.0
• PNPM Version: 10.18.3
• Node Path: C:\Program Files\nodejs\node.exe
• Pro User ID: ****iLCm
• Telemetry ID: b05f6e4b-e2b6-44d2-aaa1-151815ce1fcb
• Model: anthropic:claude-opus-4-6 | customId: undefined

Settings

• Selected Model: anthropic:claude-opus-4-6
• Chat Mode: local-agent
• Auto Approve Changes: n/a
• Dyad Pro Enabled: true
• Thinking Budget: n/a
• Runtime Mode: host
• Release Channel: beta
• Auto Fix Problems: false
• Native Git: true

Logs

[2026-03-24 14:51:52.287] [warn]  (retryWithRateLimit) Get Supabase project logs for veqjojgugpzeswtwzopv: Rate limited (attempt 3/9), retrying in 8199ms
[2026-03-24 14:52:02.171] [warn]  (retryWithRateLimit) Get Supabase project logs for veqjojgugpzeswtwzopv: Rate limited (attempt 6/9), retrying in 30000ms
[2026-03-24 14:52:02.460] [warn]  (retryWithRateLimit) Get Supabase project logs for veqjojgugpzeswtwzopv: Rate limited (attempt 7/9), retrying in 30000ms
[2026-03-24 14:52:02.943] [warn]  (retryWithRateLimit) Get Supabase project logs for veqjojgugpzeswtwzopv: Rate limited (attempt 5/9), retrying in 30000ms
[2026-03-24 14:52:03.464] [warn]  (retryWithRateLimit) Get Supabase project logs for veqjojgugpzeswtwzopv: Rate limited (attempt 8/9), retrying in 30000ms
[2026-03-24 14:52:05.371] [warn]  (retryWithRateLimit) Get Supabase project logs for veqjojgugpzeswtwzopv: Rate limited (attempt 1/9), retrying in 2199ms
[2026-03-24 14:52:06.491] [warn]  (retryWithRateLimit) Get Supabase project logs for veqjojgugpzeswtwzopv: Rate limited (attempt 6/9), retrying in 30000ms
[2026-03-24 14:52:07.140] [warn]  (retryWithRateLimit) Get Supabase project logs for veqjojgugpzeswtwzopv: Rate limited (attempt 5/9), retrying in 30000ms
[2026-03-24 14:52:07.975] [warn]  (retryWithRateLimit) Get Supabase project logs for veqjojgugpzeswtwzopv: Rate limited (attempt 8/9), retrying in 30000ms
[2026-03-24 14:52:10.329] [warn]  (retryWithRateLimit) Get Supabase project logs for veqjojgugpzeswtwzopv: Rate limited (attempt 2/9), retrying in 4070ms
[2026-03-24 14:52:10.348] [warn]  (retryWithRateLimit) Get Supabase project logs for veqjojgugpzeswtwzopv: Rate limited (attempt 1/9), retrying in 2003ms
[2026-03-24 14:52:13.021] [warn]  (retryWithRateLimit) Get Supabase project logs for veqjojgugpzeswtwzopv: Rate limited (attempt 2/9), retrying in 4392ms
[2026-03-24 14:52:13.038] [warn]  (retryWithRateLimit) Get Supabase project logs for veqjojgugpzeswtwzopv: Rate limited (attempt 6/9), retrying in 30000ms
[2026-03-24 14:52:15.042] [warn]  (retryWithRateLimit) Get Supabase project logs for veqjojgugpzeswtwzopv: Rate limited (attempt 3/9), retrying in 8162ms
[2026-03-24 14:52:15.293] [warn]  (retryWithRateLimit) Get Supabase project logs for veqjojgugpzeswtwzopv: Rate limited (attempt 1/9), retrying in 2148ms
[2026-03-24 14:52:15.332] [warn]  (retryWithRateLimit) Get Supabase project logs for veqjojgugpzeswtwzopv: Rate limited (attempt 8/9), retrying in 30000ms
[2026-03-24 14:52:16.303] [warn]  (retryWithRateLimit) Get Supabase project logs for veqjojgugpzeswtwzopv: Rate limited (attempt 6/9), retrying in 30000ms
[2026-03-24 14:52:17.543] [warn]  (retryWithRateLimit) Get Supabase project logs for veqjojgugpzeswtwzopv: Rate limited (attempt 3/9), retrying in 8057ms
[2026-03-24 14:52:17.599] [warn]  (retryWithRateLimit) Get Supabase project logs for veqjojgugpzeswtwzopv: Rate limited (attempt 2/9), retrying in 4154ms

[dyad-assistant]

This issue might be a duplicate of existing issues. Please check:

• [session report] tool_use invalid input error with Claude Opus on long sessions #2879: Same Anthropic tool_use/tool_result formatting error via litellm.BadRequestError with Claude Opus (confidence: high)

You might want to check the status update from the team based on this earlier comment.

Feel free to ignore if this doesn't address your specific case.

[wwwillchen-bot]

Session Debug Analysis

Root cause identified: Bug in maybeAppendRetryReplayForRetry in local_agent_handler.ts that breaks parallel tool-call grouping during stream retry replay.

What happened

1. The user's session had a long assistant turn with ~27 tool calls (schema reads, file reads, SQL executions, file writes)
2. At 14:50:53, the stream terminated with a transient error, triggering the retry mechanism (pass 1/3)
3. The retry replayed the completed tool exchanges into the message history, but split parallel tool results into separate messages
4. The Anthropic API rejected the malformed payload at messages.13

The bug

When the AI makes parallel tool calls (e.g., reading 3 files at once), the stream events arrive as:

tool-call A, tool-call B, tool-call C, tool-result A, tool-result B, tool-result C

The Anthropic API requires:

assistant: [call-A, call-B, call-C]
tool:      [result-A, result-B, result-C]   ← ALL results in one message

But maybeAppendRetryReplayForRetry (line ~1538) creates a new tool message for each tool-result event:

assistant: [call-A, call-B, call-C]   ← 3 tool_use blocks
tool:      [result-A]                  ← only 1 result — API rejects this
tool:      [result-B]                  ← orphaned
tool:      [result-C]                  ← orphaned

Fix

When adding a tool-result to replay messages, merge into the previous tool message if one exists (consecutive tool-result messages should be grouped):

// Replace lines 1538-1549 in local_agent_handler.ts
flushPendingAssistantMessage();
const lastReplayMsg = replayMessages[replayMessages.length - 1];
if (lastReplayMsg?.role === "tool" && Array.isArray(lastReplayMsg.content)) {
  lastReplayMsg.content.push({
    type: "tool-result",
    toolCallId: event.toolCallId,
    toolName: event.toolName,
    output: toToolResultOutput(event.output),
  });
} else {
  replayMessages.push({
    role: "tool",
    content: [{
      type: "tool-result",
      toolCallId: event.toolCallId,
      toolName: event.toolName,
      output: toToolResultOutput(event.output),
    }],
  });
}

Additional findings

• 15+ Supabase rate limit failures during the session (heavy log polling)
• Likely related to [session report] tool_use invalid input error with Claude Opus on long sessions #2879 (same replay code path, different manifestation)

[wwwillchen]

@beaugast thanks for reporting this, looks like our previous fix had an issue, and we'll do another fix soon.