{"version":"2.1.314","anchor":"update-settings-allows-effortlevel-auto-under-a-new-parame","canonical_anchor":"update-settings-allows-effortlevel-auto-under-a-new-parame","heading":"Effort level can be \"auto\"","tier":"notice","area":"Effort","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/update-settings-allows-effortlevel-auto-under-a-new-parame","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Effort level can be \"auto\"\n\n`update_settings` can accept `effortLevel` \"auto\", and the effort command now shows \"auto\" when no effort level is set\n\n**Unclear.** What condition allows `auto` to be accepted is not stated.\n\n**What**\n\nThe effort level controls how much reasoning the model puts into a reply. Two changes concern an \"auto\" value for it:\n\n- `update_settings` now accepts `effortLevel` set to \"auto\", but only when an additional true\/false option in the same request is set to true. Without it, \"auto\" is not accepted.\n\n- The effort command now prints `Effort level: auto` when no effort level is set. Before, it printed a computed default label instead.\n\n**Why**\n\nIf you check your effort level without having set one, you now see \"auto\" rather than the name of a default level. Tools that change settings through `update_settings` can set \"auto\" only together with the extra option.\n\n- Area: Effort\n- Names: `effortLevel`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}