{"version":"2.1.314","anchor":"effort-cap-applied-only-to-the-current-turn-onward","canonical_anchor":"effort-cap-applied-only-to-the-current-turn-onward","heading":"An effort cap can limit effort from the latest turn onward","tier":"internal","area":"Effort","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/effort-cap-applied-only-to-the-current-turn-onward","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### An effort cap can limit effort from the latest turn onward\n\nClaude Code can cap the effort level of messages from the start of the latest turn onward, leaving earlier messages unchanged\n\n**Unclear.** It is not clear what sets the effort cap or whether a user can set it.\n\n**What**\n\nEffort is how much work the model puts into a reply. Claude Code works out the effort level for each message in a conversation, and that calculation now accepts an optional effort cap. When a cap is given, messages from the start of the latest turn onward are lowered to the cap if they were above it. Earlier messages keep the effort they had. Before, effort was taken straight from each reply.\n\n**Why**\n\nThis points to a way of putting a ceiling on effort that applies to new work in a conversation and leaves earlier history alone.\n\n- Area: Effort\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}