What probably matters to youSection of the release
Unclear Whether these shortcuts apply on every platform and build is not stated.
What
The effort level sets how much thinking Claude puts into a reply, and you normally change it with /effort. There are now keyboard actions to step it up or down.
Keys: the default chat key map binds shift+up to chat:increaseEffort and shift+down to chat:decreaseEffort. Which builds or conditions fill in these bindings is not shown.
Cache warning: if a step would miss the prompt cache, a store of recent input that makes replies cheaper and faster, an effort confirmation prompt appears first. Stepping up when the next step would be max shows "stops below max · /effort max to set it".
Tip: a new tip, effort-step-keys, says to press these keys to "raise or lower the effort level for this session". It shows only when both bindings are set as plain keys and a feature check passes.
Hints: the shortcuts help panel gets a new entry under the same check, and a dimmed "change effort" hint can appear on screen under a condition that was not resolved.
Status line: the effort status line can now end with "may wait for your next message" instead of "/effort".
Why
You can change effort without typing a command. Watch for the confirmation prompt, since changing effort mid-conversation can cost a cache miss, and for the status line saying the new level may only apply from your next message.
Read from
Names in the bundlechat:increaseEffortchat:decreaseEffort
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhether these shortcuts apply on every platform and build is not stated.
Anthropic's release notes agreeFixed /effort not warning about a prompt cache miss in plan mode when the plan model differs from the session model
