Repository navigation
fix(ui): a tool result with an error output renders as output-error - #441
Merged
Merged
Conversation
robelest
force-pushed
the
fix/162-tool-error-output
branch
from
October 30, 2026 20:21
94bc79c to
e499a7e
Compare
commit: |
Closed
robelest
force-pushed
the
fix/162-tool-error-output
branch
from
October 30, 2026 21:48
e499a7e to
decc349
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
A tool that throws is stored with an
error-text(orerror-json) output, buttoUIMessagesonly treated a result as an error viaisErrorormessage.error, so it rendered asoutput-available. The tool-result mapping now also treatserror-text/error-jsonoutputs asoutput-error, with the value (JSON-stringified forerror-json) aserrorText, whether or not the call is on the same page.Fixes #162.