{"version":"2.1.304","anchor":"effort-status-shows-plain-auto-when-no-concrete-level-is-k","canonical_anchor":"effort-status-shows-plain-auto-when-no-concrete-level-is-k","heading":"Effort status shows plain auto when no level is known","tier":"notice","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/effort-status-shows-plain-auto-when-no-concrete-level-is-k","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Effort status shows plain auto when no level is known\n\nThe effort status now reads 'Effort level: auto' when no current level can be worked out, instead of always adding a 'currently' value\n\n**What**\n\nEffort is how much thinking Claude puts into a reply. When effort is set to auto and Claude Code cannot work out the level in use right now, the status message now reads \"Effort level: auto\". Before, it always added \"(currently ...)\" after auto, even when there was no real value to show.\n\n**Why**\n\nThe status no longer shows a misleading \"currently\" value.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}