MCP and skills code now receives its storage explicitly instead of reading a process-wide location.
What's wrong with this entry?
Functions that used to read configuration from a process-wide location now receive it as an argument, including MCP server connection and tool fetching, skills syncing and classification, grove config caching, subscription and auth lookups, and tips and nudge handling. Auth lookups are now cached under a single "oauth-tokens" key.
storageV5
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