{"version":"2.1.281","anchor":"model-picker-effort-choice-is-passed-to-the-caller-instead","canonical_anchor":"model-picker-effort-choice-is-passed-to-the-caller-instead","heading":"Model picker: effort choice is passed to the caller instead of written to state directly","tier":"notice","area":"Models","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/model-picker-effort-choice-is-passed-to-the-caller-instead","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Model picker: effort choice is passed to the caller instead of written to state directly\n\nThe model picker now hands your effort choice to the screen that opened it instead of saving it itself\n\n**Unclear.** The finding does not say whether the effort is still saved in the same places as before once the caller receives it.\n\n**What**\n\nThe model picker is the menu where you choose which model Claude Code uses, and for some models an effort level. It no longer saves the effort level into the session or your settings itself. Instead it records a `tengu_model_command_menu_effort` event and passes the effort to whatever opened the picker. It only does this when you actually changed the effort and the chosen model supports it. The `skipSettingsWrite` option was removed.\n\n**Why**\n\nPicking a model without touching effort no longer passes an effort along, and whatever opened the picker now decides what happens to the effort you chose.\n\n- Area: Models\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}