{"version":"2.1.311","anchor":"pewter-owl-model-override-can-come-from-a-passed-in-config-o","canonical_anchor":"pewter-owl-model-override-can-come-from-a-passed-in-config-o","heading":"An internal model override is read from a different place","tier":"internal","area":"Models","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/pewter-owl-model-override-can-come-from-a-passed-in-config-o","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### An internal model override is read from a different place\n\nAn internal model override is now read from settings handed to the lookup instead of a shared store, with no visible change\n\n**What**\n\nClaude Code has an internal model override called pewter_owl_model. It used to be read from a single shared settings store. It is now read from a settings object handed to the lookup when it runs. When the server sends nothing for this override, it still falls back to an empty value.\n\n**Why**\n\nThis changes where the value comes from inside Claude Code. It does not change anything you can see.\n\n- Flag `tengu_pewter_owl_model`: Not enough to say (read for one account on one subscription tier against v2.1.311; this account: no value returned, anonymous baseline: no value returned, compiled default: not a boolean we can read) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Models\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}