{"version":"2.1.238","anchor":"model-picker-names-both-models-when-a-session-override-is-in","canonical_anchor":"model-picker-names-both-models-when-a-session-override-is-in","heading":"Model picker names both models when a session override is in place","tier":"notice","area":"Models","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/model-picker-names-both-models-when-a-session-override-is-in","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### Model picker names both models when a session override is in place\n\nThe model picker now names both your session model and configured model when they differ.\n\n**What**\n\nWhen you have a session-scoped model on top of a different configured one, the picker now names both and says the pick replaces both, instead of saying the session model will be undone. Models not otherwise in the list appear as extra entries labelled \"Current model\" and \"Base model\".\n\n**Details**\n\n- The effort you choose in the picker is now applied as the session's effort rather than written to `effortLevel` in your user settings, so it does not outlive the session.\n- The notice is built at runtime around the two model names; the fixed part is \"). Selecting a model here replaces both.\"\n\n**Evidence**\n\n`). Selecting a model here replaces both.`\n\n- Area: Models\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}