{"version":"2.1.295","anchor":"plugin-option-enum-validation-inverted","canonical_anchor":"plugin-option-enum-validation-inverted","heading":"Plugin options with a value outside the allowed list are handled differently","tier":"notice","area":"Plugins","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/plugin-option-enum-validation-inverted","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Plugin options with a value outside the allowed list are handled differently\n\nClaude Code changed how it treats a plugin option whose value is not one of that option's allowed choices\n\n**Unclear.** It is not known whether invalid option values are now kept or dropped.\n\n**What**\n\nSome plugins (add-on packages for Claude Code) have options limited to a fixed list of choices. When an option holds a value that is not on its list, Claude Code still warns that it reads as unset, but what it does with the value afterwards changed. The check also now looks at a different field of the option, which looks like the correction of a mistake.\n\n**Why**\n\nIf a plugin option of yours holds a value outside its allowed choices, Claude Code may now keep or drop it differently than before.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}