@devries-cameron20 / composio-1 / commits / 9c29abb5c
Fork 0

Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.

docs(changelog): note that an explicit additionalProperties: false still closes a property-less object

The open-by-default claim and the Backward Compatibility carve-out both read as unconditional for objects that name no properties. An explicit additionalProperties: false closes such an object, and Python raises on unknown keys it previously dropped through Pydantic's default extra="ignore" - the same drop-to-raise transition already documented for objects that declare properties.

jkomyno committed Aug 7, 2026 at 23:07 UTC 9c29abb5c7d4b7eb5e8c091f8361152f321348ee
1 file changed +2 -2
docs/content/changelog/08-06-26-free-form-tool-arguments.mdx
+2 -2
@@ -19,7 +19,7 @@ A tool argument declared as a bare `{"type": "object"}` — with no `properties`
19
20 ### What Changed
21
22 -An object schema that names no properties is now treated as open: arbitrary content is accepted and preserved, at the root, nested inside another object, and inside array items.
22 +An object schema that names no properties is now treated as open, unless it sets `additionalProperties: false`: arbitrary content is accepted and preserved, at the root, nested inside another object, and inside array items.
23
24 **Before:**
25
@@ -143,6 +143,6 @@ Accepting and preserving free-form object content is backward compatible: payloa
143
144 The two unknown-key rejections described above (Python agentic providers and the Claude Agent SDK provider) are two of the three behavior changes at call time. The third is [Python dynamic-key validation](#dynamic-keys-apply-only-where-they-should): a key that used to be dropped in silence now raises a `ValidationError` when it does not match the `patternProperties` or `additionalProperties` schema that claims it.
145
146 -`additionalProperties: true` still opts an object out of unknown-key rejection, and so does declaring no properties. Neither opts out of the third change: if the object also carries `patternProperties` or a schema-valued `additionalProperties`, its keys are validated against those schemas. Objects with no dynamic-key constraints at all are unaffected.
146 +`additionalProperties: true` still opts an object out of unknown-key rejection. Declaring no properties does too, unless the object sets `additionalProperties: false` — an explicit `false` closes it, and Python now raises on the unknown keys it used to drop there, the same drop-to-raise transition as the first change. Neither opt-out covers the third change: if the object carries `patternProperties` or a schema-valued `additionalProperties`, its keys are validated against those schemas. An open object with no dynamic-key constraints is unaffected by it.
147
148 The remaining changes happen earlier, when the tool's schema is first read rather than when it is called: an invalid dynamic-key schema now fails instead of being ignored. In Python that is a raise while the tool is wrapped, covering an invalid reference, regular expression, or Draft 7 subschema. In the CLI it is a schema compile failure, covering an invalid `patternProperties` regular expression or an unresolvable reference inside a dynamic-key subschema. Only tools whose `patternProperties` or schema-valued `additionalProperties` carry one of those defects are affected.