{"version":"2.1.196","anchor":"model-alias-resolution","canonical_anchor":"model-alias-resolution","heading":"Model Alias Resolution","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.196\/e\/model-alias-resolution","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.196","markdown":"### Model Alias Resolution\n\nA model alias system is now active that maps logical family names (\"opus\", \"sonnet\", \"haiku\") to their current provider-specific model IDs, resolved per-provider (first-party, Bedrock, Vertex, etc.). This powers model resolution across providers without hardcoding per-family logic at each call site.\n\n**Details**\n\n- Aliases are looked up via `aQs(name, provider)` which checks per-provider overrides before falling back to a default.\n- Model selection (`$xe` for opus, `qHn` for sonnet, `L4r` for haiku) now goes through alias resolution before falling back to the baked-in catalog entries.\n- Org-default model handling (`C4r`, `ZFd`, `uW`, `zai`, `Gw`) is now built on top of alias resolution.\n\n**Evidence**\n\nNew alias resolution logic (search for `\"opus\"` in model alias context, or the new `aQs` call path)"}