{"version":"2.1.280","anchor":"a-ui-nudge-banners-gating-switched-from-a-model-name-blackl","canonical_anchor":"a-ui-nudge-banners-gating-switched-from-a-model-name-blackl","heading":"A UI nudge banner's gating switched from a model-name blacklist to session-activity checks","tier":"internal","area":"Elsewhere","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/a-ui-nudge-banners-gating-switched-from-a-model-name-blackl","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### A UI nudge banner's gating switched from a model-name blacklist to session-activity checks\n\nA UI nudge banner now decides whether to show based on session activity instead of the model name\n\n**Unclear.** The finding does not say which banner this is or what condition now causes it to show or hide.\n\n**What**\n\nA function controlling a UI nudge banner used to decide whether to show it purely by checking the current model name against a blacklist (various `claude-3-*`, `opus-4-*`, `sonnet-4-*`, and `haiku-4-5` models). It now instead takes the session's loading state and transcript content as input, computing its result from whether the session is loading, the transcript's content, and another gate function, and no longer checks the model name at all.\n\n**Why**\n\nThis makes the banner's visibility depend on what's actually happening in the current session rather than which model is selected, so the same banner logic now applies consistently regardless of model.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}