{"version":"2.1.292","anchor":"effort-is-carried-into-turn-state-and-the-ccr-token-expiry-p","canonical_anchor":"effort-is-carried-into-turn-state-and-the-ccr-token-expiry-p","heading":"Effort level carried into session state, and a state file locked to your user","tier":"internal","area":"Internal Helpers","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/effort-is-carried-into-turn-state-and-the-ccr-token-expiry-p","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### Effort level carried into session state, and a state file locked to your user\n\nThe effort level from a request is now copied into session state when unset, and a lock or state file is written readable only by you\n\n**What**\n\nTwo small changes:\n\n- The effort level from a request, the setting for how much work Claude puts into a reply, is copied into the session's state when that state has none.\n\n- A lock or state file is now written with permissions 0600, so only your user account can read or change it.\n\n**Why**\n\nThese are small changes to behaviour and to file security.\n\n- Area: Internal Helpers\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}