{"version":"2.1.246","anchor":"interrupting-a-turn-no-longer-looks-like-rejecting-a-tool","canonical_anchor":"interrupting-a-turn-no-longer-looks-like-rejecting-a-tool","heading":"Interrupting a turn no longer looks like rejecting a tool","tier":"notice","area":"Interrupts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/interrupting-a-turn-no-longer-looks-like-rejecting-a-tool","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Interrupting a turn no longer looks like rejecting a tool\n\nInterrupting mid-turn now tells the model the turn was stopped, not that you rejected the tool.\n\n**What**\n\nPressing interrupt mid-turn now marks the pending tool results as interrupted rather than reusing the \"user rejected this\" wording, so the model is told the turn was stopped instead of being told you refused that particular tool.\n\n**Details**\n\n- Tool results carry `toolDenialKind: \"interrupted\"` when the abort reason is a turn abort.\n- Genuine rejections keep the previous user-rejected path and its rejection text.\n\n**Evidence**\n\n`toolDenialKind: \"interrupted\"`\n\n- Area: Interrupts\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 3\/5"}