Expose failure_error_function in Agent.as_tool #2179
Merged
+107
−1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
seratch
requested changes
Dec 14, 2025
seratch
approved these changes
Dec 16, 2025
Member
|
Sorry, can you resolve the conflicts? Your changes here look good to me. |
Nekowaii
force-pushed
the
feat/as-tool-failure-error-function
branch
from
58ae138 to
dea3f43
Compare
Contributor
Author
|
Done. I rebased and fixed the conflicts. Thanks. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Expose
failure_error_functioninAgent.as_tool()and pass it through to@function_tool(...).Motivation
When an
Agentis wrapped viaas_tool(), exceptions raised during the nestedRunner.run(...)(including failures triggered by hosted tools like Code Interpreter, file/web search, etc.) are currently converted into a generic tool error string by the defaultfunction_toolerror handler. This makes it difficult to:This change keeps the default behavior unchanged, but allows opting into exception propagation via
failure_error_function=None.