IDE connections can be told auto mode was only a fallback and which default would be offered instead.
tengu_maple_pier Off in both readingsThe flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.
This account: off · anonymous baseline: off · compiled default in v2.1.232: 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.232. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
The payload sent when an IDE connects gained two optional fields: whether auto mode is in effect only because no settings source picked a mode, and which defaultMode from user settings a one-time nudge would offer to replace.
- Both fields are sent only when the entrypoint is the VS Code extension.
- Whether the nudge is eligible at all is decided separately by the
tengu_maple_piergate, which is off absent a server value.
permission_mode_from_default_fallback
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
Stale editor bridge connections are dropped instead of read
Both mention integration
-
v2.1.234
Git remote URLs can no longer smuggle a different host
Both mention integration
-
v2.1.236
Change detection ignores custom diff drivers and submodules
Both mention integration