More config writes, logout and cache clearing name their storage explicitly.
What's wrong with this entry?
The default nudge, organisation default model tracking, daemon install prompt dismissal, GitHub repository path tracking, the feedback survey timestamp and Chrome onboarding all write through a named storage handle now. Logout takes credentials directly, session cache clearing and post-compaction cleanup take the handle, and transcript path validation only runs when the newer storage backend is active.
if (fr() && t !== void 0 && o === void 0)
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