{"version":"2.1.117","anchor":"model-deprecation-remapping-system","canonical_anchor":"model-deprecation-remapping-system","heading":"Model Deprecation Remapping System","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.117\/e\/model-deprecation-remapping-system","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.117","markdown":"### Model Deprecation Remapping System\n\n**What**\n\nExpanded model deprecation tracking with retirement dates and automatic remapping guidance for deprecated models.\n\n**Details**\n\n- New entries for Claude Opus 4 (retiring June 15, 2026 on first-party), Claude Opus 4.1, and Claude Sonnet 4 (retiring June 15, 2026 on first-party)\n- Models with `remappedTo` field tell users what replacement to use (e.g., Opus 4 and 4.1 remap to \"the latest Opus\")\n- Replaces the older deprecation table that only covered Claude 3 Opus, Claude 3.7 Sonnet, and Claude 3.5 Haiku\n- The system displays warnings via `addNotification` when a model is approaching retirement\n\n**Evidence**\n\nModel deprecation table with `remappedTo` field (search for `\"remappedTo\"`) \u2014 `Vq8` at line ~544460"}