{"version":"2.1.315","anchor":"tool-result-persistence-no-longer-uses-the-inline-text-path","canonical_anchor":"tool-result-persistence-no-longer-uses-the-inline-text-path","heading":"Large tool results are saved by a single size limit","tier":"notice","area":"Tool Results","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315\/e\/tool-result-persistence-no-longer-uses-the-inline-text-path","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315","markdown":"### Large tool results are saved by a single size limit\n\nClaude Code now uses a single size limit to decide when a large tool result is saved and replaced with a preview\n\n**What**\n\nWhen a tool returns a very large result, Claude Code can save it and give Claude a shorter preview instead. A tool is one of the actions Claude can take, such as reading a file or running a command. The way Claude Code decides this has changed.\n\nIt used to take part of the text inline and record where it was cut off. Now, if the host app says it takes such content inline, the result is passed on unchanged. Otherwise Claude Code applies a single size limit.\n\n**Why**\n\nThis changes when large tool outputs are replaced by a saved preview.\n\n- Area: Tool Results\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}