Unclear It is not clear whether the stored names are the same switches as before or renamed ones.
Two places that read a server-controlled switch no longer spell out the switch's name where they read it. The name is now held elsewhere and looked up:
- The place that read
tengu_glimmering_finchnow reads a stored name. The texttengu_glimmering_finchno longer appears anywhere in this build. - The place that read
tengu_silly_shorealso now reads a stored name.
In both places, if the server sends nothing, the switch still counts as on.
When a switch's name is no longer written out, it becomes harder to follow that switch from one release to the next. If the stored name is a different switch, settings the server had for the old name would not carry over.
tengu_glimmering_finch 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.319: 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.
tengu_silly_shore 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.319: 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.319. It isn't a statement about your account. What a flag value here can and cannot tell you
It is not clear whether the stored names are the same switches as before or renamed ones.