Unclear What the two new remote switches change in practice is not clear.
When Claude Code asks the model for a reply and nothing comes back, it retries. It now recognises a separate case: a reply that stopped because it was suspended. Those get their own number of retries before Claude Code falls back to its normal retry handling.
Two new remote switches set or limit retry values. Both are on unless they are switched off remotely. Claude Code also now records how retries tied to filtered output end.
A reply that stalled because the computer went to sleep, for example, now has its own allowance for retrying instead of being treated like any other missing reply.
tengu_tidy_cloud 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.290: 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.
tengu_eager_rain 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.290: 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.290. It isn't a statement about your account. What a flag value here can and cannot tell you
What the two new remote switches change in practice is not clear.
New in this build: tengu_eager_rain