Recovering from broken conversations

[edmondop]

I often find myself in a broken conversation liek so:

Error: {"error":{"message":"messages.44: tool_use ids were found without tool_result blocks immediately after: toolu_vrtx_017CEaU5fCLh8TXiuFQYjUif. Each tool_use block must have a corresponding tool_result block in the next message.","code":"invalid_request_body"}}

I try to use gd to edit the conversation and remove past and then save and rty agai, but it doesn't work as expected. After doing CTRL+S in the debug window and CTRL + C when I go back to the chat, if I type a new message, it says "no message to submit"

[Jufralice]

I often have same problem.

[olimorris]

This indicates that a tool errored, so correcting this, should be the fix.

[edmondop]

Removing the last message from the chat leaves me in a “no message to submit state” do you know how I can cause a tool failure to create a mini reproducer to share ?

…

On Thu, Aug 7, 2025 at 4:21 AM Oli ***@***.***> wrote: This indicates that a tool errored, so correcting this, should be the fix. — Reply to this email directly, view it on GitHub <#1939 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAGGOKPMB6OWZC2S2D2VS533MMEAPAVCNFSM6AAAAACDI2WKC6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTIMBTGEYTSMI> . You are receiving this because you authored the thread.Message ID: <olimorris/codecompanion.nvim/repo-discussions/1939/comments/14031191@ github.com>

[edmondop]

@olimorris would you be able to document a standard operating procedure to repair a tool failure?

[olimorris]

The fixes in v17.16.0 should largely fix this from happening. Previously, I wasn't handling any errors which could arise in the success or error handlers of tools. So this would cause the issue of orphaned tool calls leading to those type of error messages.

If you notice it is occurring then please let me know the responsible tool. It might well be there are exceptions in how it executes which we're not capturing.