{"version":"2.1.248","anchor":"model-switch-consent-can-no-longer-fire-twice","canonical_anchor":"model-switch-consent-can-no-longer-fire-twice","heading":"Model-switch consent can no longer fire twice","tier":"notice","area":"Models","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/model-switch-consent-can-no-longer-fire-twice","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Model-switch consent can no longer fire twice\n\n\/model can no longer apply a second model change or print a duplicate notice.\n\n**What**\n\nA stale consent callback from `\/model` can no longer apply a second model change or print a duplicate \"Kept model as\" notice. The picker now tracks whether it has already been answered and returns early if so.\n\n**Details**\n\n- Both the `\/model` command and the model-switch component carry a generation counter and an already-handled flag, checked before the model change is applied.\n- The user-facing strings moved into shared constants with no wording change.\n\n**Evidence**\n\n`Kept model as `\n\n- Area: Models\n- Names: `\/model`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5"}