messages.87: `tool_use` ids were found without `tool_result` blocks immediately

[JacquesGariepy]

Description

messages.87: tool_use ids were found without tool_result blocks immediately after: toolu_012AdeqFL8nhF99UwDf3QHgw. Each tool_use block must have a corresponding tool_result block in the next message

Plugins

No response

OpenCode version

No response

Steps to reproduce

No response

Screenshot and/or share link

No response

Operating System

No response

Terminal

No response

[uuc110]

• 1 same issue continuously even in 1.1.40

[prolific]

Still facing this in 1.1.53

Makes the current session completely useless. Can't continue and even with /undo it continues to show same error.
The only solution is to start a new one which is a big waste of tokens and time.

[joecwu]

I’ve experienced this issue with the Claude model. When I switch to Gemini, it works. It could be that some tools are incompatible with the Claude model.

[rekram1-node]

can anyone send me a session this happened in? opencode export > session.json

[robertyates]

i can't send the full trace due to privacy, but here is the error message

`tool_use` ids were found without `tool_result` blocks immediately after: toolu_018SHDkB3Q3R6oyrrWzb2fje. Each `tool_use` block must have a corresponding `tool_result` block in the next message.

when i look in the logs for that id i only get one reference which is here

{                                                                                    
            "id": "prt_c440403b90013VHY5TQbZ0H07r",                                                                                 
            "sessionID": "ses_3bc033f4dffe4p39JbC2Ix0iRF",                                                                          
            "messageID": "msg_c4403fb2a001Wn7YPcpeY4fq7c",                                                                          
            "type": "tool",                                                                                                         
            "callID": "toolu_018SHDkB3Q3R6oyrrWzb2fje",                                                                             
            "tool": "edit",                                                                                                         
            "state": {                                                                                                              
              "status": "error",                                                                                                    
              "input": {},                                                                                                          
              "error": "Tool execution aborted",                                                                                    
              "time": {                                                                                                             
                "start": 1770667684458,                                                                                             
                "end": 1770667684458                                                                                                
              }                                                                                                                     
            }                                                                                                                       
          }

i am fairly confident that this was caused by parallel tool calls both trying to edit

it looks as though opencode prevents the second edit from ever firing and so it never gets a tool response. I am still digging a little bit, but wanted to post this if it helps.

UPDATE: this is what my coding agent says, it chewed on this for a while

But I think I found the actual bug. Look at the tool-error handler in processor.ts:

⏺ Read 1 file (ctrl+o to expand)

⏺ Line 198: if (match && match.state.status === "running") - the tool-error handler only processes errors for tools in "running" status.
   If the SDK emits a tool-error for a tool that's still in "pending" status (because tool-call was never processed), the error is
  silently ignored. The tool stays "pending", eventually gets cleaned up as "aborted", but the SDK's proper error result is dropped.

  Same issue exists for tool-result at line 179: if (match && match.state.status === "running").

  The fix is to also handle these events for "pending" tools:

⏺ Update(~/Documents/GitHub/opencode/packages/opencode/src/session/processor.ts)

────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
 Edit file
 ../opencode/packages/opencode/src/session/processor.ts
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
 171                  }
 172                  case "tool-result": {
 173                    const match = toolcalls[value.toolCallId]
 174 -                  if (match && match.state.status === "running") {                                                                
 174 +                  if (match && (match.state.status === "running" || match.state.status === "pending")) {                          
 175 +                    const startTime =                                                                                             
 176 +                      match.state.status === "running" ? match.state.time.start : Date.now()                                      
 177                      await Session.updatePart({
 178                        ...match,
 179                        state: {
...
 183                          metadata: value.output.metadata,
 184                          title: value.output.title,
 185                          time: {
 184 -                          start: match.state.time.start,                                                                          
 186 +                          start: startTime,                                                                                       
 187                            end: Date.now(),
 188                          },
 189                          attachments: value.output.attachments,
...
 197
 198                  case "tool-error": {
 199                    const match = toolcalls[value.toolCallId]
 198 -                  if (match && match.state.status === "running") {                                                                
 200 +                  if (match && (match.state.status === "running" || match.state.status === "pending")) {                          
 201 +                    const startTime =                                                                                             
 202 +                      match.state.status === "running" ? match.state.time.start : Date.now()                                      
 203                      await Session.updatePart({
 204                        ...match,
 205                        state: {
...
 207                          input: value.input ?? match.state.input,
 208                          error: (value.error as any).toString(),
 209                          time: {
 206 -                          start: match.state.time.start,                                                                          
 210 +                          start: startTime,                                                                                       
 211                            end: Date.now(),
 212                          },
 213                        },

[DamianB-BitFlipper]

This happened to me on v1.2.2 using opus 4.6 (computer went asleep while the model was running, maybe related), but seems unrecoverable.