In cloud sessions, where Claude Code runs on a hosted machine rather than your own computer, Claude Code now watches how busy the machine's processors are. The work runs inside a sandbox, a walled-off environment with limited access to the system.
If the sandbox uses 90% or more of all its CPUs for a set length of time, Claude Code stops the session's running shell tasks (commands it started in the terminal) and every process those commands started. It then tells Claude that this happened. A second, shorter time limit only records the event without stopping anything.
Both time limits come from a setting sent by Anthropic's servers. When the server sends nothing, both limits are effectively endless, so the watchdog does nothing unless it is switched on remotely.
Long, CPU-heavy commands in cloud sessions can now be killed automatically. If a build or test run in a cloud session stops unexpectedly, sustained full CPU use is one possible reason.
tengu_hidden_giraffe 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.314: not a boolean we can read
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.314. It isn't a statement about your account. What a flag value here can and cannot tell you
New in this build: tengu_hidden_giraffe