{"version":"2.1.290","anchor":"trailing-whitespace-path-error-reworded-with-a-new-error-cod","canonical_anchor":"trailing-whitespace-path-error-reworded-with-a-new-error-cod","heading":"Clearer error for file paths that end in a space, with a new error code","tier":"notice","area":"File Paths","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/trailing-whitespace-path-error-reworded-with-a-new-error-cod","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Clearer error for file paths that end in a space, with a new error code\n\nA path ending in white space now gets a clearer refusal, and its error code changed from 2 to 20\n\n**What**\n\nWhen a file path ends in white space (a space or a similar blank character), the error has been reworded. It now says the tool refuses such a path and cannot open a file whose own name ends in white space. The old text said the path \"does not name one file\".\n\nThe error code for this case changed from 2 to 20.\n\n**Why**\n\nThe message is easier to understand for both you and Claude. If you have scripts or tools that react to Claude Code's error codes, they will now see 20 for this case.\n\n- Area: File Paths\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}