{"version":"2.1.267","anchor":"effort-level-can-now-be-set-per-turn-not-just-per-session","canonical_anchor":"effort-level-can-now-be-set-per-turn-not-just-per-session","heading":"Effort level can now be adjusted per turn based on permission layers","tier":"notice","area":"Effort","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267\/e\/effort-level-can-now-be-set-per-turn-not-just-per-session","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267","markdown":"### Effort level can now be adjusted per turn based on permission layers\n\nClaude Code's effort level can now be influenced per turn, not just per session, via a new turnEffort value\n\n**What**\n\n- A new `turnEffort` value, derived from the active permission layers, now feeds into the effort-resolution logic used across compaction, the `\/effort` command's output, the `${CLAUDE_EFFORT}` prompt template substitution, and agent session metadata, alongside the existing model default and any explicit override.\n\n- The effort-resolution function gained a `turnEffort` option that, when the model has a defined capability lookup, takes priority in choosing the effective effort level, and it now also affects the effort suffix text shown to users (e.g. \"with X effort\").\n\n- Subagent (Task) tool calls now pass their own `turnEffort`, computed from the subagent's permission layers, into the permission checks used for command-execution and model resolution.\n\n**Why** Allows the effort level to vary within a session based on context, such as which permission layer is active for a given turn or subagent, rather than being fixed for the whole session.\n\n- Area: Effort\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}