{"version":"2.1.295","anchor":"tool-execution-tracks-same-turn-errored-tool-uses-and-queued","canonical_anchor":"tool-execution-tracks-same-turn-errored-tool-uses-and-queued","heading":"Tools now know which other calls in the same turn failed","tier":"internal","area":"Tools","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/tool-execution-tracks-same-turn-errored-tool-uses-and-queued","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Tools now know which other calls in the same turn failed\n\nWhen Claude runs several tools at once, each tool now knows which others in that turn errored and which are waiting their turn\n\n**What**\n\nWhen Claude asks to use several tools in one turn (one round of responding), Claude Code now keeps track of two more things and hands them to each tool:\n\n- Failed calls: which other tool uses in the same turn ended in an error.\n\n- Waiting calls: which calls are queued behind one that must run on its own.\n\nBefore, tools were only told which other tool uses were in the same turn.\n\n**Why**\n\nTools get more context about what their neighbours in a turn did, such as whether an earlier one failed.\n\n- Area: Tools\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}