{"version":"2.1.268","anchor":"model-clamp-warning-threading-refactored-still-single-fire","canonical_anchor":"model-clamp-warning-threading-refactored-still-single-fire","heading":"Model-clamp warning threading refactored, still single-fire per message","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/model-clamp-warning-threading-refactored-still-single-fire","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Model-clamp warning threading refactored, still single-fire per message\n\nThe plan-mode model-limit warning logic was restructured internally but still shows the warning only once per message\n\n**What**\n\nThe function that enforces a model 'clamp' in plan mode (limiting which model can be used) now returns both the chosen model and a `clampWarning` value together, instead of just the model. The logic for deduplicating and logging that warning, which used to live inside the clamp function itself, now lives in the calling code.\n\n**Why**\n\nThis is an internal restructuring of how the warning is passed around; the behavior a user sees, one warning per message at most, stays the same.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}