{"version":"2.1.286","anchor":"non-string-tool-results-get-converted-to-text-before-sending","canonical_anchor":"non-string-tool-results-get-converted-to-text-before-sending","heading":"Unusual tool results are turned into text before they are sent","tier":"notice","area":"Tools","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286\/e\/non-string-tool-results-get-converted-to-text-before-sending","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286","markdown":"### Unusual tool results are turned into text before they are sent\n\nTool results that are neither text nor a list are now converted to text, and cut short if long, before Claude Code sends them\n\n**Unclear.** It is not clear when this conversion runs or whether any setting controls it.\n\n**What**\n\nA tool result is the output a tool hands back to Claude after it runs, such as the contents of a file or the output of a command. Claude Code now checks the tool results in your messages before sending them. If a result is something other than empty, a piece of text or a list, Claude Code turns it into text:\n\n- Long results are cut short, with a note such as `[N more characters of this tool result not shown]`.\n\n- If the result cannot be turned into text at all, it is replaced by `[tool result could not be converted to text]`.\n\n**Why**\n\nA badly formed tool result could otherwise make the whole request to the model fail. Converting it to text keeps the conversation going.\n\n- Area: Tools\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}