Claude Code has a stall detector that checks at regular intervals whether its main processing loop (the part that handles work one piece at a time) has frozen. It used to check at one fixed rate. It can now switch to a slower rate after a quiet period and return to the normal rate as soon as there is work again.
- Remote sessions, where
CLAUDE_CODE_REMOTEis set, pass in settings for this slower idle rate. - Telling whether a stall came from the process being paused and resumed is now optional, and logs show
n/awhen it is off. - The detector can now be stopped.
The flag that controls this detector is off unless it is switched on remotely. It read on for this site's account and for the anonymous baseline, having switched on since the previous reading.
Fewer checks while nothing is happening means fewer timer wake-ups, mostly in remote sessions.
tengu_event_loop_stall 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.288: 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.288. It isn't a statement about your account. What a flag value here can and cannot tell you
The code path no longer asks a flag before it runs.
Which parts of Claude Code besides remote sessions use the slower idle rate is not established.