{"version":"2.0.58","anchor":"concurrent-tool-error-propagation","canonical_anchor":"concurrent-tool-error-propagation","heading":"Concurrent Tool Error Propagation","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.0.58\/e\/concurrent-tool-error-propagation","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.0.58","markdown":"### Concurrent Tool Error Propagation\n\n**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.\n\n**Details:**\n\n- New `hasErrored` flag tracks error state across concurrent tools\n- `getAbortReason()` distinguishes between user interruption and sibling errors\n- Synthetic error messages clearly indicate why tools were aborted\n- **Evidence**: Class `y30` at line 411600, `createSyntheticErrorMessage()` at line 411636, `getAbortReason()` at line 411653 in v2.0.58"}