{"version":"2.1.312","anchor":"effort-command-accepts-more-default-values","canonical_anchor":"effort-command-accepts-more-default-values","heading":"\/effort handles 'default' and 'auto' better and tracks the effort sent","tier":"use","area":"Effort","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312\/e\/effort-command-accepts-more-default-values","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312","markdown":"### \/effort handles 'default' and 'auto' better and tracks the effort sent\n\n\/effort now reads 'default' and 'auto' from what you typed, its auto keyword comes from a helper, and sessions record the effort sent each turn\n\n**Unclear.** It is not known which extra values the command now accepts.\n\n**What**\n\nThe `\/effort` command sets how much effort the model spends on its answers. Several things around it changed.\n\n- The check for `default` or `auto` now looks at the trimmed text you typed, plus one extra check. Before, it tested a variable that was never set, which looks like a bug.\n\n- The usage text, suggestions and the tip about switching away from `max` now get the auto keyword from a function instead of the fixed word `auto`, so the word can differ. The default option reads \"Use the default effort level for your model\".\n\n- When a reply starts, the session now records the effort that was sent and the effort for the turn, from `sentEffort`, `turnEffort` and `effort`.\n\n**Why**\n\n`\/effort default` and `\/effort auto` may now work where they did not before. The name of the auto option can vary, so check the usage text if it looks different.\n\n- Area: Effort\n- Names: `\/effort`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}