Group of 3 Use it now
String settings can now declare a fixed set of options, rendered as a picker in MCP and plugin config forms
What
- Config-style setting fields can now declare a fixed
optionsarray (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 orrequired: truemust be set. - MCP server config forms now render such a field as a
selectfield withoptionsand a hint, instead of always showing free text. - Plugin-provided string settings that declare an
optionsarray now render as a pick-to-commit enum/choice control instead of free text.
Why
This 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.
Names in the bundleoptions
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Added since
A small documentation edit on Hooks reference touched a line naming options after this was published.
Hooks are user-defined shell commands, HTTP endpoints, MCP tool calls, LLM prompts, or subagents that execute automatically at specific points in Claude Code's lifecycle. Claude Code fires the same hook events wherever it runs: sessions in…hooks see the edit
Confirmed since
Anthropic's documentation has since written up options, on Agent SDK reference - Python.
| `betas` | `list[SdkBeta]` | `[]` | Beta features to enable. See [`SdkBeta`](#sdkbeta) for available options |agent-sdk/python see the edit
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up options, on Agent SDK reference - Python.
Anthropic's release notes agree
Added mouse support to the /config panel in fullscreen mode: the wheel scrolls the settings list, a click on a setting's value changes it…