{"version":"2.1.318","anchor":"detection-of-zsh-command-not-found-errors","canonical_anchor":"detection-of-zsh-command-not-found-errors","heading":"Claude Code recognises zsh errors from commands starting with =","tier":"notice","area":"Bash Tool","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/detection-of-zsh-command-not-found-errors","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Claude Code recognises zsh errors from commands starting with =\n\nClaude Code now spots zsh errors like `command not found: =foo`, which come from a word starting with `=`\n\n**Unclear.** It is not clear what Claude Code does once it recognises the error.\n\n**What**\n\nIn the zsh shell, a word starting with `=` is expanded, and a failed expansion gives an error such as `command not found: =foo`. Claude Code now recognises this error.\n\n**Why**\n\nThis probably lets Claude Code handle or explain the error when a command starts with `=`.\n\n- Area: Bash Tool\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}