{"version":"2.1.281","anchor":"plugin-hosted-buttons-carry-options-and-are-matched-by-reque","canonical_anchor":"plugin-hosted-buttons-carry-options-and-are-matched-by-reque","heading":"Plugin-hosted buttons carry options and are matched by requestId","tier":"internal","area":"Plugins","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/plugin-hosted-buttons-carry-options-and-are-matched-by-reque","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Plugin-hosted buttons carry options and are matched by requestId\n\nButtons hosted for plugins now store their own options and can be looked up by the request they belong to\n\n**Unclear.** The finding does not say what the per-button options contain or what a reader sees differently.\n\n**What**\n\nClaude Code keeps a list, or registry, of buttons that plugins (add-ons that extend Claude Code) can place on screen. Each button in that list now stores its own `options`, and a lookup can be narrowed to the buttons belonging to one `requestId`, an identifier for a single request.\n\n**Why**\n\nIn practice this lets Claude Code find the right button for a given request instead of treating all hosted buttons alike.\n\n- Area: Plugins\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}