{"version":"2.1.238","anchor":"permission-errors-separated-from-disk-full-errors","canonical_anchor":"permission-errors-separated-from-disk-full-errors","heading":"Permission errors separated from disk-full errors","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/permission-errors-separated-from-disk-full-errors","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### Permission errors separated from disk-full errors\n\nClaude Code can now tell a permission-denied write from a genuinely full disk.\n\n**What**\n\nFilesystem failures are now sorted into two groups instead of one: the existing out-of-space and handle-exhaustion codes, and a new set of permission codes, so callers can tell \"cannot write here\" from \"disk is full\".\n\n**Details**\n\n- The new set covers EACCES, EPERM, and EROFS.\n\n**Evidence**\n\n`new Set([\"EACCES\", \"EPERM\", \"EROFS\"])`\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}