{"version":"2.1.282","anchor":"jsx-ui-button-supports-a-primary-or-secondary-variant","canonical_anchor":"jsx-ui-button-supports-a-primary-or-secondary-variant","heading":"Buttons in the built-in UI toolkit get a primary or secondary style","tier":"internal","area":"UI Toolkit","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/jsx-ui-button-supports-a-primary-or-secondary-variant","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### Buttons in the built-in UI toolkit get a primary or secondary style\n\nButtons built with Claude Code's JSX UI toolkit now accept a `variant` of \"primary\" or \"secondary\", and any other value is an error\n\n**Unclear.** It is not clear who can use this toolkit, for example plugins or generated artifacts.\n\n**What**\n\nClaude Code includes a small toolkit for building interface pieces with JSX, a way of writing layouts that looks like HTML. Its Button now accepts a `variant` option set to \"primary\" or \"secondary\". Any other value is rejected with an error, and the error message listing a Button's allowed options now includes `variant`.\n\n**Why**\n\nThis matters to anyone writing custom interface pieces with this toolkit: buttons can now be marked as the main action or a secondary one, and a misspelled variant fails loudly rather than being ignored.\n\n- Area: UI Toolkit\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}