{"version":"2.1.236","anchor":"agent-toolset-config-entries-are-now-typed-per-tool","canonical_anchor":"agent-toolset-config-entries-are-now-typed-per-tool","heading":"Agent toolset config entries are now typed per tool","tier":"use","area":"SDK","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236\/e\/agent-toolset-config-entries-are-now-typed-per-tool","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236","markdown":"### Agent toolset config entries are now typed per tool\n\nAgent toolset config entries now use a typed shape per tool, affecting typed-language SDK callers.\n\n**What**\n\nEach 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.\n\n**Details**\n\n- MCP toolset `configs` entries deliberately do not gain `type` or the web settings.\n\n**Evidence**\n\n`Code written against an SDK where all tools shared one config type must update how it constructs entries.`\n\n- Area: SDK\n- Names: `configs`, `type`\n- Tier: Use it now\n- Useful: 2\/5\n- Signal: 2\/5"}