{"version":"2.1.271","anchor":"plugin-config-settings-support-a-new-enumchoice-type","canonical_anchor":"config-schema-string-settings-can-now-declare-a-fixed-picke","heading":"Settings can now offer a fixed list of choices instead of free text","tier":"use","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/plugin-config-settings-support-a-new-enumchoice-type","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### Settings can now offer a fixed list of choices instead of free text\n\nString settings can now declare a fixed set of options, rendered as a picker in MCP and plugin config forms\n\n**What**\n\n- Config-style setting fields can now declare a fixed `options` array (1-64 character strings, no control or bidirectional characters, no leading\/trailing spaces, case-insensitive-unique), for string-type, non-multiple, non-sensitive fields; a default among the options or `required: true` must be set.\n\n- MCP server config forms now render such a field as a `select` field with `options` and a hint, instead of always showing free text.\n\n- Plugin-provided string settings that declare an `options` array now render as a pick-to-commit enum\/choice control instead of free text.\n\n**Why**\n\nThis lets settings with a fixed set of valid values (for MCP servers or plugins) be presented as a picker instead of a free-text box, reducing invalid input.\n\n- Area: Elsewhere\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 2\/5"}