You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
SessionsArea: what it touches
ImprovementsKind: in v2.1.296,
ImprovementsSection of the release
Unclear It is not known which sessions meet the condition that lets Claude Code stop the running turn.
What
You can press the left arrow key to send a session to the background, so it keeps running while you do something else. A turn is one round of Claude working on your request. When this happens inside the same running Claude Code process, Claude Code now:
stops the turn that was in progress
waits up to 2 seconds for it to finish stopping
does not send any messages that were still queued after that
Text you typed for a message that was not sent is kept in your input history, which you can bring back with the up arrow key. Claude Code tells you it was not sent.
Before, queued messages were carried over and nothing stopped the running turn.
Why
Pressing left arrow in the middle of a turn now interrupts that turn instead of racing with it. Watch for messages you queued just before backgrounding: they may not be sent, and you will need to recall them from history and send them again.
Read from
Feature flag
tengu_bg_leftarrow_inprocessNot enough to say
Nothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.296: on
These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not known which sessions meet the condition that lets Claude Code stop the running turn.
Anthropic's release notes agree[Code Review] Fixed the Code Review check sometimes staying "in progress" on a pull request after the review finished; it now shows the…
