{"version":"2.1.268","anchor":"prompt-time-model-id-remapping-breezy-horizon-gets-stric","canonical_anchor":"prompt-time-model-id-remapping-breezy-horizon-gets-stric","heading":"Prompt-time model-id remapping (\"breezy_horizon\") gets stricter validation and a self-mapping warning","tier":"internal","area":"Model Routing","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/prompt-time-model-id-remapping-breezy-horizon-gets-stric","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Prompt-time model-id remapping (\"breezy_horizon\") gets stricter validation and a self-mapping warning\n\nModel-id remapping via CLAUDE_CODE_BREEZY_HORIZON now validates ids more strictly and warns on no-op mappings\n\n**What**\n\nThe mechanism that lets a model id be substituted for another before a prompt is sent (driven by the `CLAUDE_CODE_BREEZY_HORIZON` environment variable or server-supplied config) now validates candidate model ids more precisely. It also warns distinctly when a mapping's target is the same model it's meant to replace, reporting that the mapping \"maps nothing,\" instead of silently treating it as a no-op.\n\n**Why**\n\nThis makes a misconfigured or pointless model-id mapping visible as a warning instead of failing silently, making it easier to notice when a substitution rule isn't actually doing anything.\n\n- Area: Model Routing\n- Names: `CLAUDE_CODE_BREEZY_HORIZON`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}