{"version":"2.1.293","anchor":"tool-result-type-distinguishes-message-to-user-result","canonical_anchor":"tool-result-type-distinguishes-message-to-user-result","heading":"Messages to the user are now told apart from ordinary tool results","tier":"internal","area":"Tools","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/tool-result-type-distinguishes-message-to-user-result","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### Messages to the user are now told apart from ordinary tool results\n\nClaude Code now separates tool results that carry a message for the user, and marks interrupted turns that end on an unanswered tool call\n\n**Unclear.** What difference this makes to what a user sees is not shown.\n\n**What**\n\nClaude Code now sorts a tool result (what comes back after Claude uses a tool) into one of two kinds. If the result carries a message meant for you and does not end Claude's turn, it is treated as a message to the user. Otherwise it is an ordinary tool result.\n\nA turn that was interrupted can also now be marked as ending on a tool call that never got an answer.\n\n**Why**\n\nThis changes how interrupted turns and messages addressed to you are represented inside Claude Code.\n\n- Area: Tools\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}