{"version":"2.1.273","anchor":"new-cli-diagnostics-for-malformed-tools-entries","canonical_anchor":"new-cli-diagnostics-for-malformed-tools-entries","heading":"New CLI diagnostics for malformed --tools entries","tier":"use","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/new-cli-diagnostics-for-malformed-tools-entries","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### New CLI diagnostics for malformed --tools entries\n\nThe --tools flag now gives specific warnings for common typos and formatting mistakes\n\n**What**\n\nThe `--tools` flag, which restricts which built-in tools Claude Code can use, now parses its entries more carefully and warns about specific common mistakes:\n\n- an entry that doesn't match any recognized built-in tool name (possible typo)\n\n- a rule written with parentheses where a plain tool name was meant\n\n- an exclusion prefix (like `!`) separated from the tool name by a stray space\n\n- a bare exclusion prefix with nothing after it\n\n**Why**\n\nThese warnings catch malformed `--tools` entries that would otherwise silently fail to do what was intended, such as a tool being unexpectedly withheld because of a typo, without any explanation.\n\n- Area: Elsewhere\n- Names: `--tools`\n- Tier: Use it now\n- Useful: 2\/5\n- Signal: 1\/5"}