The stall detector's counters were moved into a class with a single instance. Same 200 ms interval, same threshold and sleep/wake heuristic, same [event-loop-stall] detector started line, same tengu_event_loop_stall event fields, and the same terminal mode reassertion after a suspected sleep/wake.
- Two neighbouring singletons got the same treatment: a run-budget tracker exposing
isOverBudget,recordRunandfirstPolicySkipFor, and a deduper exposingmarkIfChanged. Nothing in the surrounding code shows what those two control.
[event-loop-stall] detector started
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
tengu_event_loop_stall Gate removed from the codeThis release deleted the gate from the code while it was still reading on for the account this site reads, so the code path no longer asks a flag before running.
This account: on · anonymous baseline: on · compiled default in v2.1.227: 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.227. It isn't a statement about your account. What a flag value here can and cannot tell you
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
The code path no longer asks a flag before it runs.