{"version":"2.1.282","anchor":"bash-output-lost-diagnosis-now-covers-disk-quota-edquot","canonical_anchor":"bash-output-lost-diagnosis-now-covers-disk-quota-edquot","heading":"Lost command output is now explained when your disk quota is full","tier":"notice","area":"Bash Tool","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/bash-output-lost-diagnosis-now-covers-disk-quota-edquot","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### Lost command output is now explained when your disk quota is full\n\nWhen a command's output is lost, Claude Code can now tell you your disk quota is full or the disk is out of space, and suggest a fix\n\n**What**\n\nWhen output from a command Claude Code ran is lost, Claude Code tries to explain why. It still checks free space and free file slots on the disk. If neither explains it, it now looks at the actual error and gives a specific message:\n\n- Disk quota full: \"Your disk quota is full on the filesystem with Claude Code's temp directory\".\n\n- Disk out of space: a matching message.\n\nBoth suggest restarting Claude Code with `CLAUDE_CODE_TMPDIR` set, which moves its temporary files to another place. The disk checks also no longer give up early when the free-space reading comes back negative.\n\n**Why**\n\nPeople on machines with storage limits per user are now told why their commands printed nothing, and what to change.\n\n- Area: Bash Tool\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}