What's wrong with this entry?
Anonymous. No account, no email.
What: When one tool in a concurrent execution fails, sibling tools are now gracefully aborted with a clear "Sibling tool call errored" message instead of continuing independently.
Details:
- New
hasErroredflag tracks error state across concurrent tools getAbortReason()distinguishes between user interruption and sibling errors- Synthetic error messages clearly indicate why tools were aborted
- Evidence: Class
y30at line 411600,createSyntheticErrorMessage()at line 411636,getAbortReason()at line 411653 in v2.0.58