{"version":"2.1.318","anchor":"bash-tail-input-capture-checks-free-disk-space-and-gives-up","canonical_anchor":"bash-tail-input-capture-checks-free-disk-space-and-gives-up","heading":"Saving output piped into tail now stops when disk space runs low","tier":"notice","area":"Bash Tool","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/bash-tail-input-capture-checks-free-disk-space-and-gives-up","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Saving output piped into `tail` now stops when disk space runs low\n\nThe file that keeps what was piped into `tail` now checks free disk space and gives up when space is low\n\n**What**\n\nWhen a Bash command pipes output into `tail`, Claude Code can save the full output to a file. That file used to be kept with no disk checks. It now checks free disk space when it starts, while it runs and at the end. It stops saving when:\n\n- Free disk space is low\n\n- The file reaches a size cap\n\n- The disk check itself fails\n\nWhen this happens you see \"Bash: not saving what was piped into tail to a file (the command is not affected)\". The command still runs normally. The usage data Claude Code reports now records free space at the start and whether saving was given up.\n\n**Why**\n\nLarge piped output can no longer fill your disk through this file.\n\n- Area: Bash Tool\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}