Unclear Two further conditions it checks were not identified, so it is unclear whether setting the variable alone turns this on for a local user.
When you resume a session whose last prompt was interrupted, Claude Code can now treat that turn as one that can be picked up again, even if some tool calls (actions Claude had started, such as running a command or editing a file) were cut off before they got an answer. With this switched on, those cut-off calls stay visible in the resumed conversation.
This is controlled by the CLAUDE_CODE_RESUME_SHOWS_CUT_OFF_CALLS environment variable, which is a named value you set in your shell before starting Claude Code. It does nothing unless it is set to true. It also has to pass a server-side safety switch, which stays out of the way unless the server sends otherwise, and two further internal conditions.
- Local use: you get this only by setting
CLAUDE_CODE_RESUME_SHOWS_CUT_OFF_CALLSyourself. - Hosted remote sessions: when Claude Code restarts the same session on a new worker, it sets the variable to
1for you and uses a different resume prompt.
The note Claude receives about calls that were lost has been reworded, and a new version of it tells Claude that such calls are no longer shown above.
After an interruption, Claude can see which actions it had started and not finished, instead of resuming without them. For remote sessions that get restarted, this happens without any setting.
tengu_mutable_phoenix_killswitch Not enough to sayNothing 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.309: off
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.
tengu_vast_journal Not enough to sayNothing 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.309: 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.
Read once, for one account on one subscription tier, against v2.1.309. It isn't a statement about your account. What a flag value here can and cannot tell you
Two further conditions it checks were not identified, so it is unclear whether setting the variable alone turns this on for a local user.
New in this build: tengu_mutable_phoenix_killswitch