{"version":"2.1.319","anchor":"shell-output-file-size-poll-no-longer-overlaps-output-file","canonical_anchor":"shell-output-file-size-poll-no-longer-overlaps-output-file","heading":"Background command output checks no longer pile up on slow disks","tier":"notice","area":"Bash","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/shell-output-file-size-poll-no-longer-overlaps-output-file","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Background command output checks no longer pile up on slow disks\n\nBackground shell commands now skip an output-size check while the last one is still running, and delete spare output files at once\n\n**What**\n\nWhile a shell command runs in the background, Claude Code checks the size of its output file every so often, and stops the command if the file grows too large. It now skips a check when the previous one has not finished yet.\n\nA spare output file the command no longer needs is now deleted right away. Before, it was deleted a moment later, and that step was skipped if the command had been moved to the background.\n\n**Why**\n\nOn a slow file system, size checks no longer stack up behind one another, and spare output files are no longer left behind.\n\n- Area: Bash\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}