{"version":"2.1.318","anchor":"tool-result-envelopes-passed-through-under-a-gate","canonical_anchor":"tool-result-envelopes-passed-through-under-a-gate","heading":"One kind of relayed message can now carry a tool result","tier":"internal","area":"Remote Control","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/tool-result-envelopes-passed-through-under-a-gate","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### One kind of relayed message can now carry a tool result\n\nA kind of relayed message that used to produce nothing can now pass on a tool result when a condition holds, and a text mix-up was fixed\n\n**Unclear.** It is not clear what condition makes this kind of message carry a tool result.\n\n**What**\n\nA tool call is a single action Claude takes, such as reading a file, and a tool result is what comes back from it. When Claude Code relays or replays messages, one kind of message used to produce nothing. When a certain condition holds, it now produces a tool result entry.\n\nIn the same place, the text used for messages not written by the user was being taken from the wrong value. That is now corrected.\n\n**Why**\n\nThis changes what relayed or replayed messages contain.\n\n- Area: Remote Control\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}