{"version":"2.1.238","anchor":"session-reasoning-effort-and-configured-effort-are-now-track","canonical_anchor":"session-reasoning-effort-and-configured-effort-are-now-track","heading":"Session reasoning effort and configured effort are now tracked separately","tier":"notice","area":"Reasoning Effort","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/session-reasoning-effort-and-configured-effort-are-now-track","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### Session reasoning effort and configured effort are now tracked separately\n\nClearing in-session reasoning effort now falls back to your configured effort instead of nothing.\n\n**What**\n\nEffort is stored as two values, the one the running session picked and the one resolved from CLI flags, environment and settings, with everything reading the session value first and the configured value otherwise. Clearing the in-session effort now falls back to your configured effort instead of to nothing, and a settings-derived effort survives session-level changes.\n\n**Details**\n\n- The status line, model picker, permission-layer override and the `effort_level` telemetry field all read through the same resolver.\n- A helper clears the last-reported effort so the current value gets re-reported after a change.\n\n**Evidence**\n\n`return e.sessionEffort ?? e.settingsEffort;`, `sessionEffort`\n\n- Area: Reasoning Effort\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}