Unclear Whether CLAUDE_CODE_RESUME_INTERRUPTED_TURN is set by default in remote sessions is not known.
When a remote session is picked up again after its worker restarts, Claude Code can now account for tool calls (actions such as running a command or reading a file) that the previous worker had already carried out and recorded, but that the transcript never marked as finished. A worker is the process that runs your session on a remote machine.
This applies when the environment variable CLAUDE_CODE_RESUME_INTERRUPTED_TURN is set. In that case Claude Code:
- treats those recorded but unfinished tool calls as part of the turn that was interrupted
- reads the session transcript a second time, keeping every branch of the conversation, to find the original tool request when it is missing from the main line
The resume logic is also tied to a remotely controlled switch that defaults to off. The flag server returned it on for this site's account and for an anonymous baseline, a change since the reading before that; no reading has been taken under this release yet.
When a remote worker restarts in the middle of a turn, less of the work it was doing is lost or repeated.
tengu_eager_pillow Off by default, switched on for this accountThe shipped code defaults this off, and the flag server returned on for the one account this site reads on this version. That is the reading that makes the entry above worth a second look, and it still says nothing about your account.
This account: on · anonymous baseline: on · compiled default in v2.1.292: 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.
Read once, for one account on one subscription tier, against v2.1.292. It isn't a statement about your account. What a flag value here can and cannot tell you
Whether `CLAUDE_CODE_RESUME_INTERRUPTED_TURN` is set by default in remote sessions is not known.