{"version":"2.0.52","anchor":"tool-result-persistence","canonical_anchor":"tool-result-persistence","heading":"Tool Result Persistence","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.0.52\/e\/tool-result-persistence","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.0.52","markdown":"### Tool Result Persistence\n\n**What:** Large tool outputs (>400KB) are now saved to disk instead of being truncated, allowing Claude to access the full data later.\n\n**How it works:** When a tool produces output exceeding 400KB with `ENABLE_TOOL_RESULT_SIZE_LIMIT` enabled, the output is:\n\n- Saved to `~\/.claude\/projects\/<project>\/tool-results\/<tool>-<timestamp>\/result.{txt|json}`\n- A 2KB preview is shown inline\n- Claude receives instructions on how to explore the full file\n\n**Example output:**\n\n`<persisted-output> Output too large (1.5 MB). Full output saved to: ~\/.claude\/projects\/...\/tool-results\/Bash-1701234567890\/result.txt Preview (first 2.0 KB): [preview content...] ... You can explore this file using: - Read tool to view portions of the file - Grep tool to search for patterns - Bash with jq to query JSON data - Bash with head\/tail for beginning\/end <\/persisted-output>` **Details:**\n\n- Automatically detects JSON output and creates `.json` files with `jq` usage examples\n- Tool result files are automatically granted read permission (no prompts needed)\n- Falls back to truncation if file writing fails\n- **Evidence:** `$_2()` at line 403698, `if5()` at line 403760, `nf5()` at line 403783"}