Settings writes now name their storage, so config can follow whichever backend a session uses.
tengu_hover_rest 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.236: on
Read once, for one account on one subscription tier, against v2.1.236. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
Many settings writes now name the storage they are writing to instead of assuming the local config file. This is what allows configuration to follow whichever storage backend a session uses.
- Converted call sites include onboarding completion, install method, OAuth role storage, clearing the primary API key, iTerm2 and tmux setup flags, overage consent, the remote dialog seen flag, Apple Terminal setup, the first-token date, expanded todo display and the fullscreen upsell counter.
- Which storage the handle actually points at is decided by the
tengu_hover_restflag.
await sn((d) => ({ ...d, installMethod: "global" }), t)
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.239
Remote Control bridge sessions reject foreign --mcp-config entries
Both mention config
-
v2.1.239
Remote sessions drop disallowed --mcp-config servers instead of failing the run
Both mention config
-
v2.1.239
More specific explanations when an --mcp-config is ignored
Both mention config