Agent toolset config entries now use a typed shape per tool, affecting typed-language SDK callers.
What's wrong with this entry?
Each entry in an agent toolset's configs array is now one of eight per-tool shapes, picked by a type field that appears in responses even when you omit it in requests. Dict-based SDKs (Python, TypeScript, Ruby) are unaffected; Go, Java, C#, and PHP callers must build entries from the per-tool types.
- MCP toolset
configsentries deliberately do not gaintypeor the web settings.
Code written against an SDK where all tools shared one config type must update how it constructs entries.
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