{"version":"2.1.277","anchor":"command-output-error-message-classifier-expanded-from-3-to-5","canonical_anchor":"command-output-error-message-classifier-expanded-from-3-to-5","heading":"Command-output error message classifier expanded from 3 to 5 pattern checks","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/command-output-error-message-classifier-expanded-from-3-to-5","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### Command-output error message classifier expanded from 3 to 5 pattern checks\n\nCommand output errors now get checked against five specific message patterns instead of three before falling back to generic text\n\n**Unclear.** Which two new patterns were added and what specific errors they cover is not stated.\n\n**What**\n\nWhen a command's tool output needs to be turned into a special, more specific error message (used in non-verbose mode), Claude Code now checks it against five distinct pattern-matching functions in sequence, up from three, before falling back to its generic write or delete failure messages.\n\n**Why**\n\nThis means more kinds of command failures can now get a tailored, more informative error message instead of a generic fallback one.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}