{"version":"2.1.314","anchor":"effort-auto-message-no-longer-interpolates-the-effort-level","canonical_anchor":"effort-auto-message-no-longer-interpolates-the-effort-level","heading":"\/effort auto messages now always say \"auto\"","tier":"notice","area":"Effort","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/effort-auto-message-no-longer-interpolates-the-effort-level","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### \/effort auto messages now always say \"auto\"\n\nResetting effort with \/effort auto now confirms 'Effort level set to auto' instead of naming a computed level\n\n**What**\n\nThe `\/effort` command sets how much effort Claude puts into its answers. When you set it to `auto`, the confirmation now always reads \"Effort level set to auto\".\n\nIf the `CLAUDE_CODE_EFFORT_LEVEL` environment variable is also set, the notice now begins \"Effort set to auto for this session, but\" and goes on to say that `CLAUDE_CODE_EFFORT_LEVEL` still controls this session. Before, both messages filled in a level that Claude Code worked out at the time.\n\n**Why**\n\nThe message now matches what you asked for. If you see the notice about `CLAUDE_CODE_EFFORT_LEVEL`, unset that variable for `\/effort auto` to take effect.\n\n- Area: Effort\n- Names: `\/effort`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}