{"version":"2.1.299","anchor":"truncated-bash-output-now-says-where-the-full-start-is-saved","canonical_anchor":"truncated-bash-output-now-says-where-the-full-start-is-saved","heading":"Shortened Bash output now says which file holds the saved part","tier":"notice","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/truncated-bash-output-now-says-where-the-full-start-is-saved","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Shortened Bash output now says which file holds the saved part\n\nWhen a command's output is cut short, the notice now names the file where the start of the output was saved\n\n**What**\n\nWhen a shell command prints too much, Claude Code shortens what it gives back to Claude and keeps a saved copy. The notice that says the output was cut now names the saved file and says it holds the start of the output. If that file is gone, the notice says to run the command again.\n\n**Why**\n\nClaude can open the saved file to read the output instead of running the command a second time.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}