Skip to content

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

Release: update version (#3429)

Abir Taheerf6df489c0b2e
diff --git a/.changeset/defer-telemetry-flushes.md b/.changeset/defer-telemetry-flushes.md
deleted file mode 100644
index c722377ab..000000000
--- a/.changeset/defer-telemetry-flushes.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-'@composio/core': patch
----
-
-Defer telemetry batch and error sends so instrumentation does not wait for telemetry network requests before returning SDK results or rethrowing SDK errors.
diff --git a/.changeset/file-uploadable-list-unions.md b/.changeset/file-uploadable-list-unions.md
deleted file mode 100644
index 9606ac293..000000000
--- a/.changeset/file-uploadable-list-unions.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-'@composio/core': patch
----
-
-Fix automatic file upload/download substitution for file schemas that accept either a single file or a list of files.
-
-The file modifier now selects composed-schema branches by runtime value shape, so `anyOf(file, array<file>)` uploads or downloads each file when the tool receives a list while preserving existing single-file behavior.
diff --git a/.changeset/fix-mastra-dangling-defs-ref.md b/.changeset/fix-mastra-dangling-defs-ref.md
deleted file mode 100644
index eb092044b..000000000
--- a/.changeset/fix-mastra-dangling-defs-ref.md
+++ /dev/null
@@ -1,11 +0,0 @@
----
-'@composio/core': patch
-'@composio/mastra': patch
----
-
-Tolerate dangling `$ref` pointers in tool schemas the Composio API ships without a matching `$defs` entry. Some toolkits (e.g. `GMAIL_FETCH_EMAILS`) emit `outputParameters` with `"$ref": "#/$defs/FetchEmailsResponse"` while never declaring a top-level `$defs` block. After the strict resolver shipped with the previous Mastra fix, this caused `composio.tools.get(...)` to throw `JsonSchemaRefResolutionError` upfront, making every Gmail / Slack / Google-Calendar tool unusable through `MastraProvider`. The SDK now degrades the unresolvable branch to a permissive object schema and surfaces a single observability warning per `(toolSlug, ref)` pair instead of crashing.
-
-- `dereferenceJsonSchema` accepts a new optional second argument `{ onUnresolved?: 'throw' | 'sentinel'; onReplace?: (ref, reason) => void }`. Default behavior is unchanged (`'throw'`) — first-party / custom-tool schemas with a typo'd `$ref` still surface as a hard error. Pass `'sentinel'` to replace unresolved branches with the cycle-break sentinel (`{ type: 'object', additionalProperties: true }`) that the resolver already uses for `$ref` cycles. The replaced sentinel carries a default `description` hint so LLMs consuming the wrapped tool's schema get an in-band signal that the branch is opaque; a caller-provided `description` sibling overrides the default (Draft 2020-12 sibling-keyword merge). Safety caps (`MAX_REF_CHAIN_DEPTH`, `MAX_NODE_DEPTH`) keep throwing in both modes. New `UnresolvedRefStrategy`, `UnresolvedRefReason`, and `DereferenceJsonSchemaOptions` type exports.
-- `MastraProvider.wrapTool` opts both `inputParameters` and `outputParameters` into `'sentinel'` mode and emits one `logger.warn` per `(toolSlug, ref)` pair via the provider-scoped dedup `Set`. User-controlled segments in the warning (`tool.slug`, `toolkit.slug`, `ref`) are `JSON.stringify`d to neutralize embedded newlines / ANSI escapes / control bytes that could otherwise forge log lines (CWE-117). A matching one-shot telemetry event (`composio.mastra.wrapTool.danglingRef`) fires next to the warn so the Composio team has aggregate visibility into which toolkits are affected; the event respects `COMPOSIO_DISABLE_TELEMETRY=true`.
-- The `telemetry` instance from `@composio/core` is now publicly re-exported alongside `logger`, so providers can emit aggregate signals without reaching into the package's internals.
-- Resolvable `$defs` / `definitions` continue to be inlined exactly as before — no regression in the type-info preservation contract introduced by the previous Mastra fix.
diff --git a/.changeset/fix-mcp-empty-output-parameters.md b/.changeset/fix-mcp-empty-output-parameters.md
deleted file mode 100644
index c5c3d8e1f..000000000
--- a/.changeset/fix-mcp-empty-output-parameters.md
+++ /dev/null
@@ -1,11 +0,0 @@
----
-'@composio/core': patch
----
-
-Fix `tools.execute` (and `tools.get` / `tools.list`) failing with a `ZodError` for every tool from an MCP-backed toolkit (e.g. `granola_mcp`, `apify_mcp`, `tavily_mcp`).
-
-MCP toolkits don't declare an output schema, and the Composio API serializes that as `output_parameters: {}`. The SDK's `ParametersSchema` required `{ type: 'object', properties: {...} }`, so `transformToolCases` rejected the response and `getRawComposioToolBySlug` — called by `execute` and the list path — threw.
-
-The SDK now normalizes empty (`{}`), `null`, and missing `input_parameters` / `output_parameters` payloads to `undefined` before validation. `outputParameters` was already declared `.optional()` in the public `Tool` type, so this preserves the contract: "undefined means no declared schema." Tools that *do* declare a schema continue to be validated strictly.
-
-No public API change; no toolkit allow-list.
diff --git a/.changeset/forward-trigger-user-id.md b/.changeset/forward-trigger-user-id.md
deleted file mode 100644
index 15e17c0e0..000000000
--- a/.changeset/forward-trigger-user-id.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-"@composio/core": minor
----
-
-Forward `userId` when creating trigger instances so trigger 2FA flows can verify connected account ownership.
diff --git a/.changeset/normalize-tool-arguments-2406.md b/.changeset/normalize-tool-arguments-2406.md
deleted file mode 100644
index 0de61b4a7..000000000
--- a/.changeset/normalize-tool-arguments-2406.md
+++ /dev/null
@@ -1,28 +0,0 @@
----
-'@composio/core': patch
-'@composio/vercel': patch
-'@composio/openai-agents': patch
-'@composio/cloudflare': patch
-'@composio/anthropic': patch
-'@composio/google': patch
-'@composio/langchain': patch
-'@composio/llamaindex': patch
-'@composio/claude-agent-sdk': patch
-'@composio/mastra': patch
-'@composio/openai': patch
----
-
-fix(providers): normalize string tool-call arguments across all providers
-
-Models occasionally emit tool-call arguments as a JSON string instead of an
-object (most visibly with `COMPOSIO_MULTI_EXECUTE_TOOL` on the Vercel AI SDK),
-which broke downstream validation with errors like
-`tool_use.input: Input should be a valid dictionary`.
-
-`@composio/core` now exposes a single `normalizeToolArguments` helper, and every
-provider routes model-supplied arguments through it. Object payloads pass
-through unchanged, JSON strings are parsed, empty/`null` payloads become `{}`,
-and anything that cannot resolve to an object throws a typed
-`ComposioInvalidToolArgumentsError` instead of a raw `SyntaxError` or a silently
-forwarded malformed string. This replaces the inconsistent per-provider guards
-that previously existed only in vercel, cloudflare and openai-agents.
diff --git a/.changeset/remove-legacy-custom-tools.md b/.changeset/remove-legacy-custom-tools.md
deleted file mode 100644
index 978f24738..000000000
--- a/.changeset/remove-legacy-custom-tools.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-"@composio/core": minor
----
-
-Remove the legacy `composio.tools.createCustomTool(...)` in-memory registry API. Use Tool Router custom tools via `experimental_createTool`, `experimental_createToolkit`, and `composio.create(..., { experimental: { customTools, customToolkits } })` instead.
diff --git a/ts/packages/cli-local-tools/CHANGELOG.md b/ts/packages/cli-local-tools/CHANGELOG.md
index d15e2e62e..50f9a1e31 100644
--- a/ts/packages/cli-local-tools/CHANGELOG.md
+++ b/ts/packages/cli-local-tools/CHANGELOG.md
@@ -1,5 +1,18 @@
# @composio/cli-local-tools
+## 0.0.5
+
+### Patch Changes
+
+- Updated dependencies [22a9171]
+- Updated dependencies [93b67e8]
+- Updated dependencies [b69cef1]
+- Updated dependencies [1ba66ca]
+- Updated dependencies [a94715f]
+- Updated dependencies [ce4b213]
+- Updated dependencies [44e5458]
+ - @composio/[email protected]
+
## 0.0.4
### Patch Changes
diff --git a/ts/packages/cli-local-tools/package.json b/ts/packages/cli-local-tools/package.json
index 324c1f36d..18ca23e1a 100644
--- a/ts/packages/cli-local-tools/package.json
+++ b/ts/packages/cli-local-tools/package.json
@@ -1,6 +1,6 @@
{
"name": "@composio/cli-local-tools",
- "version": "0.0.4",
+ "version": "0.0.5",
"description": "Local tool and toolkit declarations for the Composio CLI.",
"type": "module",
"main": "dist/index.mjs",
diff --git a/ts/packages/cli/CHANGELOG.md b/ts/packages/cli/CHANGELOG.md
index 1297e2a09..50edb91b6 100644
--- a/ts/packages/cli/CHANGELOG.md
+++ b/ts/packages/cli/CHANGELOG.md
@@ -1,5 +1,19 @@
# @composio/cli
+## 0.2.32
+
+### Patch Changes
+
+- Updated dependencies [22a9171]
+- Updated dependencies [93b67e8]
+- Updated dependencies [b69cef1]
+- Updated dependencies [1ba66ca]
+- Updated dependencies [a94715f]
+- Updated dependencies [ce4b213]
+- Updated dependencies [44e5458]
+ - @composio/[email protected]
+ - @composio/[email protected]
+
## 0.2.31
### Patch Changes
diff --git a/ts/packages/cli/package.json b/ts/packages/cli/package.json
index aaba1cc6c..431299beb 100644
--- a/ts/packages/cli/package.json
+++ b/ts/packages/cli/package.json
@@ -1,6 +1,6 @@
{
"name": "@composio/cli",
- "version": "0.2.31",
+ "version": "0.2.32",
"description": "Composio CLI",
"main": "./dist/bin.mjs",
"private": true,
diff --git a/ts/packages/core/CHANGELOG.md b/ts/packages/core/CHANGELOG.md
index 27d5e36bc..73e763fc0 100644
--- a/ts/packages/core/CHANGELOG.md
+++ b/ts/packages/core/CHANGELOG.md
@@ -1,5 +1,48 @@
# @composio/core
+## 0.11.0
+
+### Minor Changes
+
+- a94715f: Forward `userId` when creating trigger instances so trigger 2FA flows can verify connected account ownership.
+- 44e5458: Remove the legacy `composio.tools.createCustomTool(...)` in-memory registry API. Use Tool Router custom tools via `experimental_createTool`, `experimental_createToolkit`, and `composio.create(..., { experimental: { customTools, customToolkits } })` instead.
+
+### Patch Changes
+
+- 22a9171: Defer telemetry batch and error sends so instrumentation does not wait for telemetry network requests before returning SDK results or rethrowing SDK errors.
+- 93b67e8: Fix automatic file upload/download substitution for file schemas that accept either a single file or a list of files.
+
+ The file modifier now selects composed-schema branches by runtime value shape, so `anyOf(file, array<file>)` uploads or downloads each file when the tool receives a list while preserving existing single-file behavior.
+
+- b69cef1: Tolerate dangling `$ref` pointers in tool schemas the Composio API ships without a matching `$defs` entry. Some toolkits (e.g. `GMAIL_FETCH_EMAILS`) emit `outputParameters` with `"$ref": "#/$defs/FetchEmailsResponse"` while never declaring a top-level `$defs` block. After the strict resolver shipped with the previous Mastra fix, this caused `composio.tools.get(...)` to throw `JsonSchemaRefResolutionError` upfront, making every Gmail / Slack / Google-Calendar tool unusable through `MastraProvider`. The SDK now degrades the unresolvable branch to a permissive object schema and surfaces a single observability warning per `(toolSlug, ref)` pair instead of crashing.
+ - `dereferenceJsonSchema` accepts a new optional second argument `{ onUnresolved?: 'throw' | 'sentinel'; onReplace?: (ref, reason) => void }`. Default behavior is unchanged (`'throw'`) — first-party / custom-tool schemas with a typo'd `$ref` still surface as a hard error. Pass `'sentinel'` to replace unresolved branches with the cycle-break sentinel (`{ type: 'object', additionalProperties: true }`) that the resolver already uses for `$ref` cycles. The replaced sentinel carries a default `description` hint so LLMs consuming the wrapped tool's schema get an in-band signal that the branch is opaque; a caller-provided `description` sibling overrides the default (Draft 2020-12 sibling-keyword merge). Safety caps (`MAX_REF_CHAIN_DEPTH`, `MAX_NODE_DEPTH`) keep throwing in both modes. New `UnresolvedRefStrategy`, `UnresolvedRefReason`, and `DereferenceJsonSchemaOptions` type exports.
+ - `MastraProvider.wrapTool` opts both `inputParameters` and `outputParameters` into `'sentinel'` mode and emits one `logger.warn` per `(toolSlug, ref)` pair via the provider-scoped dedup `Set`. User-controlled segments in the warning (`tool.slug`, `toolkit.slug`, `ref`) are `JSON.stringify`d to neutralize embedded newlines / ANSI escapes / control bytes that could otherwise forge log lines (CWE-117). A matching one-shot telemetry event (`composio.mastra.wrapTool.danglingRef`) fires next to the warn so the Composio team has aggregate visibility into which toolkits are affected; the event respects `COMPOSIO_DISABLE_TELEMETRY=true`.
+ - The `telemetry` instance from `@composio/core` is now publicly re-exported alongside `logger`, so providers can emit aggregate signals without reaching into the package's internals.
+ - Resolvable `$defs` / `definitions` continue to be inlined exactly as before — no regression in the type-info preservation contract introduced by the previous Mastra fix.
+
+- 1ba66ca: Fix `tools.execute` (and `tools.get` / `tools.list`) failing with a `ZodError` for every tool from an MCP-backed toolkit (e.g. `granola_mcp`, `apify_mcp`, `tavily_mcp`).
+
+ MCP toolkits don't declare an output schema, and the Composio API serializes that as `output_parameters: {}`. The SDK's `ParametersSchema` required `{ type: 'object', properties: {...} }`, so `transformToolCases` rejected the response and `getRawComposioToolBySlug` — called by `execute` and the list path — threw.
+
+ The SDK now normalizes empty (`{}`), `null`, and missing `input_parameters` / `output_parameters` payloads to `undefined` before validation. `outputParameters` was already declared `.optional()` in the public `Tool` type, so this preserves the contract: "undefined means no declared schema." Tools that _do_ declare a schema continue to be validated strictly.
+
+ No public API change; no toolkit allow-list.
+
+- ce4b213: fix(providers): normalize string tool-call arguments across all providers
+
+ Models occasionally emit tool-call arguments as a JSON string instead of an
+ object (most visibly with `COMPOSIO_MULTI_EXECUTE_TOOL` on the Vercel AI SDK),
+ which broke downstream validation with errors like
+ `tool_use.input: Input should be a valid dictionary`.
+
+ `@composio/core` now exposes a single `normalizeToolArguments` helper, and every
+ provider routes model-supplied arguments through it. Object payloads pass
+ through unchanged, JSON strings are parsed, empty/`null` payloads become `{}`,
+ and anything that cannot resolve to an object throws a typed
+ `ComposioInvalidToolArgumentsError` instead of a raw `SyntaxError` or a silently
+ forwarded malformed string. This replaces the inconsistent per-provider guards
+ that previously existed only in vercel, cloudflare and openai-agents.
+
## 0.10.0
### Minor Changes
diff --git a/ts/packages/core/package.json b/ts/packages/core/package.json
index 269866dd8..4e2adc635 100644
--- a/ts/packages/core/package.json
+++ b/ts/packages/core/package.json
@@ -1,7 +1,7 @@
{
"name": "@composio/core",
"type": "module",
- "version": "0.10.0",
+ "version": "0.11.0",
"description": "",
"main": "src/index.ts",
"publishConfig": {
diff --git a/ts/packages/providers/anthropic/CHANGELOG.md b/ts/packages/providers/anthropic/CHANGELOG.md
index 0a5265054..fedc102ac 100644
--- a/ts/packages/providers/anthropic/CHANGELOG.md
+++ b/ts/packages/providers/anthropic/CHANGELOG.md
@@ -1,5 +1,24 @@
# @composio/anthropic
+## 0.9.3
+
+### Patch Changes
+
+- ce4b213: fix(providers): normalize string tool-call arguments across all providers
+
+ Models occasionally emit tool-call arguments as a JSON string instead of an
+ object (most visibly with `COMPOSIO_MULTI_EXECUTE_TOOL` on the Vercel AI SDK),
+ which broke downstream validation with errors like
+ `tool_use.input: Input should be a valid dictionary`.
+
+ `@composio/core` now exposes a single `normalizeToolArguments` helper, and every
+ provider routes model-supplied arguments through it. Object payloads pass
+ through unchanged, JSON strings are parsed, empty/`null` payloads become `{}`,
+ and anything that cannot resolve to an object throws a typed
+ `ComposioInvalidToolArgumentsError` instead of a raw `SyntaxError` or a silently
+ forwarded malformed string. This replaces the inconsistent per-provider guards
+ that previously existed only in vercel, cloudflare and openai-agents.
+
## 0.9.2
### Patch Changes
diff --git a/ts/packages/providers/anthropic/package.json b/ts/packages/providers/anthropic/package.json
index 848e6e5ed..677587ea1 100644
--- a/ts/packages/providers/anthropic/package.json
+++ b/ts/packages/providers/anthropic/package.json
@@ -1,6 +1,6 @@
{
"name": "@composio/anthropic",
- "version": "0.9.2",
+ "version": "0.9.3",
"description": "Non-Agentic Provider for Anthropic in Composio SDK",
"main": "src/index.ts",
"publishConfig": {
diff --git a/ts/packages/providers/claude-agent-sdk/CHANGELOG.md b/ts/packages/providers/claude-agent-sdk/CHANGELOG.md
index f35d27223..ec840159c 100644
--- a/ts/packages/providers/claude-agent-sdk/CHANGELOG.md
+++ b/ts/packages/providers/claude-agent-sdk/CHANGELOG.md
@@ -1,5 +1,24 @@
# @composio/claude-code-agents
+## 0.9.3
+
+### Patch Changes
+
+- ce4b213: fix(providers): normalize string tool-call arguments across all providers
+
+ Models occasionally emit tool-call arguments as a JSON string instead of an
+ object (most visibly with `COMPOSIO_MULTI_EXECUTE_TOOL` on the Vercel AI SDK),
+ which broke downstream validation with errors like
+ `tool_use.input: Input should be a valid dictionary`.
+
+ `@composio/core` now exposes a single `normalizeToolArguments` helper, and every
+ provider routes model-supplied arguments through it. Object payloads pass
+ through unchanged, JSON strings are parsed, empty/`null` payloads become `{}`,
+ and anything that cannot resolve to an object throws a typed
+ `ComposioInvalidToolArgumentsError` instead of a raw `SyntaxError` or a silently
+ forwarded malformed string. This replaces the inconsistent per-provider guards
+ that previously existed only in vercel, cloudflare and openai-agents.
+
## 0.9.2
### Patch Changes
diff --git a/ts/packages/providers/claude-agent-sdk/package.json b/ts/packages/providers/claude-agent-sdk/package.json
index 6299db0c2..459f9c282 100644
--- a/ts/packages/providers/claude-agent-sdk/package.json
+++ b/ts/packages/providers/claude-agent-sdk/package.json
@@ -1,6 +1,6 @@
{
"name": "@composio/claude-agent-sdk",
- "version": "0.9.2",
+ "version": "0.9.3",
"description": "Composio provider for Claude Agent SDK",
"main": "src/index.ts",
"publishConfig": {
diff --git a/ts/packages/providers/cloudflare/CHANGELOG.md b/ts/packages/providers/cloudflare/CHANGELOG.md
index 82b3701ea..30a0a298c 100644
--- a/ts/packages/providers/cloudflare/CHANGELOG.md
+++ b/ts/packages/providers/cloudflare/CHANGELOG.md
@@ -1,5 +1,24 @@
# @composio/cloudflare
+## 0.9.3
+
+### Patch Changes
+
+- ce4b213: fix(providers): normalize string tool-call arguments across all providers
+
+ Models occasionally emit tool-call arguments as a JSON string instead of an
+ object (most visibly with `COMPOSIO_MULTI_EXECUTE_TOOL` on the Vercel AI SDK),
+ which broke downstream validation with errors like
+ `tool_use.input: Input should be a valid dictionary`.
+
+ `@composio/core` now exposes a single `normalizeToolArguments` helper, and every
+ provider routes model-supplied arguments through it. Object payloads pass
+ through unchanged, JSON strings are parsed, empty/`null` payloads become `{}`,
+ and anything that cannot resolve to an object throws a typed
+ `ComposioInvalidToolArgumentsError` instead of a raw `SyntaxError` or a silently
+ forwarded malformed string. This replaces the inconsistent per-provider guards
+ that previously existed only in vercel, cloudflare and openai-agents.
+
## 0.9.2
### Patch Changes
diff --git a/ts/packages/providers/cloudflare/package.json b/ts/packages/providers/cloudflare/package.json
index 409c0c010..1d1bf1883 100644
--- a/ts/packages/providers/cloudflare/package.json
+++ b/ts/packages/providers/cloudflare/package.json
@@ -1,6 +1,6 @@
{
"name": "@composio/cloudflare",
- "version": "0.9.2",
+ "version": "0.9.3",
"description": "",
"main": "src/index.ts",
"publishConfig": {
diff --git a/ts/packages/providers/google/CHANGELOG.md b/ts/packages/providers/google/CHANGELOG.md
index f39e8faa3..70901308f 100644
--- a/ts/packages/providers/google/CHANGELOG.md
+++ b/ts/packages/providers/google/CHANGELOG.md
@@ -1,5 +1,24 @@
# @composio/google
+## 0.9.3
+
+### Patch Changes
+
+- ce4b213: fix(providers): normalize string tool-call arguments across all providers
+
+ Models occasionally emit tool-call arguments as a JSON string instead of an
+ object (most visibly with `COMPOSIO_MULTI_EXECUTE_TOOL` on the Vercel AI SDK),
+ which broke downstream validation with errors like
+ `tool_use.input: Input should be a valid dictionary`.
+
+ `@composio/core` now exposes a single `normalizeToolArguments` helper, and every
+ provider routes model-supplied arguments through it. Object payloads pass
+ through unchanged, JSON strings are parsed, empty/`null` payloads become `{}`,
+ and anything that cannot resolve to an object throws a typed
+ `ComposioInvalidToolArgumentsError` instead of a raw `SyntaxError` or a silently
+ forwarded malformed string. This replaces the inconsistent per-provider guards
+ that previously existed only in vercel, cloudflare and openai-agents.
+
## 0.9.2
### Patch Changes
diff --git a/ts/packages/providers/google/package.json b/ts/packages/providers/google/package.json
index 28f322cef..b4710b82e 100644
--- a/ts/packages/providers/google/package.json
+++ b/ts/packages/providers/google/package.json
@@ -1,6 +1,6 @@
{
"name": "@composio/google",
- "version": "0.9.2",
+ "version": "0.9.3",
"description": "Google GenAI Provider for Composio SDK",
"main": "src/index.ts",
"publishConfig": {
diff --git a/ts/packages/providers/langchain/CHANGELOG.md b/ts/packages/providers/langchain/CHANGELOG.md
index ee1f630cd..18b2bcd25 100644
--- a/ts/packages/providers/langchain/CHANGELOG.md
+++ b/ts/packages/providers/langchain/CHANGELOG.md
@@ -1,5 +1,24 @@
# @composio/langchain
+## 0.9.3
+
+### Patch Changes
+
+- ce4b213: fix(providers): normalize string tool-call arguments across all providers
+
+ Models occasionally emit tool-call arguments as a JSON string instead of an
+ object (most visibly with `COMPOSIO_MULTI_EXECUTE_TOOL` on the Vercel AI SDK),
+ which broke downstream validation with errors like
+ `tool_use.input: Input should be a valid dictionary`.
+
+ `@composio/core` now exposes a single `normalizeToolArguments` helper, and every
+ provider routes model-supplied arguments through it. Object payloads pass
+ through unchanged, JSON strings are parsed, empty/`null` payloads become `{}`,
+ and anything that cannot resolve to an object throws a typed
+ `ComposioInvalidToolArgumentsError` instead of a raw `SyntaxError` or a silently
+ forwarded malformed string. This replaces the inconsistent per-provider guards
+ that previously existed only in vercel, cloudflare and openai-agents.
+
## 0.9.2
### Patch Changes
diff --git a/ts/packages/providers/langchain/package.json b/ts/packages/providers/langchain/package.json
index 7a8e06446..0ee705952 100644
--- a/ts/packages/providers/langchain/package.json
+++ b/ts/packages/providers/langchain/package.json
@@ -1,6 +1,6 @@
{
"name": "@composio/langchain",
- "version": "0.9.2",
+ "version": "0.9.3",
"description": "",
"main": "dist/index.js",
"publishConfig": {
diff --git a/ts/packages/providers/llamaindex/CHANGELOG.md b/ts/packages/providers/llamaindex/CHANGELOG.md
index f4520f726..0a0f1771b 100644
--- a/ts/packages/providers/llamaindex/CHANGELOG.md
+++ b/ts/packages/providers/llamaindex/CHANGELOG.md
@@ -1,5 +1,24 @@
# @composio/llamaindex
+## 0.9.3
+
+### Patch Changes
+
+- ce4b213: fix(providers): normalize string tool-call arguments across all providers
+
+ Models occasionally emit tool-call arguments as a JSON string instead of an
+ object (most visibly with `COMPOSIO_MULTI_EXECUTE_TOOL` on the Vercel AI SDK),
+ which broke downstream validation with errors like
+ `tool_use.input: Input should be a valid dictionary`.
+
+ `@composio/core` now exposes a single `normalizeToolArguments` helper, and every
+ provider routes model-supplied arguments through it. Object payloads pass
+ through unchanged, JSON strings are parsed, empty/`null` payloads become `{}`,
+ and anything that cannot resolve to an object throws a typed
+ `ComposioInvalidToolArgumentsError` instead of a raw `SyntaxError` or a silently
+ forwarded malformed string. This replaces the inconsistent per-provider guards
+ that previously existed only in vercel, cloudflare and openai-agents.
+
## 0.9.2
### Patch Changes
diff --git a/ts/packages/providers/llamaindex/package.json b/ts/packages/providers/llamaindex/package.json
index 519b31c1a..c961887a5 100644
--- a/ts/packages/providers/llamaindex/package.json
+++ b/ts/packages/providers/llamaindex/package.json
@@ -1,6 +1,6 @@
{
"name": "@composio/llamaindex",
- "version": "0.9.2",
+ "version": "0.9.3",
"description": "Agentic Provider for llamaindex in Composio SDK",
"main": "src/index.ts",
"publishConfig": {
diff --git a/ts/packages/providers/mastra/CHANGELOG.md b/ts/packages/providers/mastra/CHANGELOG.md
index d1b61867a..101a3f3f3 100644
--- a/ts/packages/providers/mastra/CHANGELOG.md
+++ b/ts/packages/providers/mastra/CHANGELOG.md
@@ -1,5 +1,30 @@
# @composio/mastra
+## 0.9.3
+
+### Patch Changes
+
+- b69cef1: Tolerate dangling `$ref` pointers in tool schemas the Composio API ships without a matching `$defs` entry. Some toolkits (e.g. `GMAIL_FETCH_EMAILS`) emit `outputParameters` with `"$ref": "#/$defs/FetchEmailsResponse"` while never declaring a top-level `$defs` block. After the strict resolver shipped with the previous Mastra fix, this caused `composio.tools.get(...)` to throw `JsonSchemaRefResolutionError` upfront, making every Gmail / Slack / Google-Calendar tool unusable through `MastraProvider`. The SDK now degrades the unresolvable branch to a permissive object schema and surfaces a single observability warning per `(toolSlug, ref)` pair instead of crashing.
+ - `dereferenceJsonSchema` accepts a new optional second argument `{ onUnresolved?: 'throw' | 'sentinel'; onReplace?: (ref, reason) => void }`. Default behavior is unchanged (`'throw'`) — first-party / custom-tool schemas with a typo'd `$ref` still surface as a hard error. Pass `'sentinel'` to replace unresolved branches with the cycle-break sentinel (`{ type: 'object', additionalProperties: true }`) that the resolver already uses for `$ref` cycles. The replaced sentinel carries a default `description` hint so LLMs consuming the wrapped tool's schema get an in-band signal that the branch is opaque; a caller-provided `description` sibling overrides the default (Draft 2020-12 sibling-keyword merge). Safety caps (`MAX_REF_CHAIN_DEPTH`, `MAX_NODE_DEPTH`) keep throwing in both modes. New `UnresolvedRefStrategy`, `UnresolvedRefReason`, and `DereferenceJsonSchemaOptions` type exports.
+ - `MastraProvider.wrapTool` opts both `inputParameters` and `outputParameters` into `'sentinel'` mode and emits one `logger.warn` per `(toolSlug, ref)` pair via the provider-scoped dedup `Set`. User-controlled segments in the warning (`tool.slug`, `toolkit.slug`, `ref`) are `JSON.stringify`d to neutralize embedded newlines / ANSI escapes / control bytes that could otherwise forge log lines (CWE-117). A matching one-shot telemetry event (`composio.mastra.wrapTool.danglingRef`) fires next to the warn so the Composio team has aggregate visibility into which toolkits are affected; the event respects `COMPOSIO_DISABLE_TELEMETRY=true`.
+ - The `telemetry` instance from `@composio/core` is now publicly re-exported alongside `logger`, so providers can emit aggregate signals without reaching into the package's internals.
+ - Resolvable `$defs` / `definitions` continue to be inlined exactly as before — no regression in the type-info preservation contract introduced by the previous Mastra fix.
+
+- ce4b213: fix(providers): normalize string tool-call arguments across all providers
+
+ Models occasionally emit tool-call arguments as a JSON string instead of an
+ object (most visibly with `COMPOSIO_MULTI_EXECUTE_TOOL` on the Vercel AI SDK),
+ which broke downstream validation with errors like
+ `tool_use.input: Input should be a valid dictionary`.
+
+ `@composio/core` now exposes a single `normalizeToolArguments` helper, and every
+ provider routes model-supplied arguments through it. Object payloads pass
+ through unchanged, JSON strings are parsed, empty/`null` payloads become `{}`,
+ and anything that cannot resolve to an object throws a typed
+ `ComposioInvalidToolArgumentsError` instead of a raw `SyntaxError` or a silently
+ forwarded malformed string. This replaces the inconsistent per-provider guards
+ that previously existed only in vercel, cloudflare and openai-agents.
+
## 0.9.2
### Patch Changes
diff --git a/ts/packages/providers/mastra/package.json b/ts/packages/providers/mastra/package.json
index d45dfdc10..02f74ad44 100644
--- a/ts/packages/providers/mastra/package.json
+++ b/ts/packages/providers/mastra/package.json
@@ -1,6 +1,6 @@
{
"name": "@composio/mastra",
- "version": "0.9.2",
+ "version": "0.9.3",
"description": "Agentic Provider for mastra in Composio SDK",
"main": "src/index.ts",
"publishConfig": {
diff --git a/ts/packages/providers/openai-agents/CHANGELOG.md b/ts/packages/providers/openai-agents/CHANGELOG.md
index 1a6ddebee..704b5b4e4 100644
--- a/ts/packages/providers/openai-agents/CHANGELOG.md
+++ b/ts/packages/providers/openai-agents/CHANGELOG.md
@@ -1,5 +1,24 @@
# @composio/openai-agents
+## 0.9.3
+
+### Patch Changes
+
+- ce4b213: fix(providers): normalize string tool-call arguments across all providers
+
+ Models occasionally emit tool-call arguments as a JSON string instead of an
+ object (most visibly with `COMPOSIO_MULTI_EXECUTE_TOOL` on the Vercel AI SDK),
+ which broke downstream validation with errors like
+ `tool_use.input: Input should be a valid dictionary`.
+
+ `@composio/core` now exposes a single `normalizeToolArguments` helper, and every
+ provider routes model-supplied arguments through it. Object payloads pass
+ through unchanged, JSON strings are parsed, empty/`null` payloads become `{}`,
+ and anything that cannot resolve to an object throws a typed
+ `ComposioInvalidToolArgumentsError` instead of a raw `SyntaxError` or a silently
+ forwarded malformed string. This replaces the inconsistent per-provider guards
+ that previously existed only in vercel, cloudflare and openai-agents.
+
## 0.9.2
### Patch Changes
diff --git a/ts/packages/providers/openai-agents/package.json b/ts/packages/providers/openai-agents/package.json
index 8242aef67..b2918bdf7 100644
--- a/ts/packages/providers/openai-agents/package.json
+++ b/ts/packages/providers/openai-agents/package.json
@@ -1,6 +1,6 @@
{
"name": "@composio/openai-agents",
- "version": "0.9.2",
+ "version": "0.9.3",
"description": "",
"main": "src/index.ts",
"publishConfig": {
diff --git a/ts/packages/providers/openai/CHANGELOG.md b/ts/packages/providers/openai/CHANGELOG.md
index 105b98313..87644bed4 100644
--- a/ts/packages/providers/openai/CHANGELOG.md
+++ b/ts/packages/providers/openai/CHANGELOG.md
@@ -1,5 +1,24 @@
# @composio/openai
+## 0.9.3
+
+### Patch Changes
+
+- ce4b213: fix(providers): normalize string tool-call arguments across all providers
+
+ Models occasionally emit tool-call arguments as a JSON string instead of an
+ object (most visibly with `COMPOSIO_MULTI_EXECUTE_TOOL` on the Vercel AI SDK),
+ which broke downstream validation with errors like
+ `tool_use.input: Input should be a valid dictionary`.
+
+ `@composio/core` now exposes a single `normalizeToolArguments` helper, and every
+ provider routes model-supplied arguments through it. Object payloads pass
+ through unchanged, JSON strings are parsed, empty/`null` payloads become `{}`,
+ and anything that cannot resolve to an object throws a typed
+ `ComposioInvalidToolArgumentsError` instead of a raw `SyntaxError` or a silently
+ forwarded malformed string. This replaces the inconsistent per-provider guards
+ that previously existed only in vercel, cloudflare and openai-agents.
+
## 0.9.2
### Patch Changes
diff --git a/ts/packages/providers/openai/package.json b/ts/packages/providers/openai/package.json
index fff979625..7a2c9f31f 100644
--- a/ts/packages/providers/openai/package.json
+++ b/ts/packages/providers/openai/package.json
@@ -1,6 +1,6 @@
{
"name": "@composio/openai",
- "version": "0.9.2",
+ "version": "0.9.3",
"description": "",
"main": "src/index.ts",
"publishConfig": {
diff --git a/ts/packages/providers/vercel/CHANGELOG.md b/ts/packages/providers/vercel/CHANGELOG.md
index 076a97cec..f06f08c5a 100644
--- a/ts/packages/providers/vercel/CHANGELOG.md
+++ b/ts/packages/providers/vercel/CHANGELOG.md
@@ -1,5 +1,24 @@
# @composio/vercel
+## 0.9.3
+
+### Patch Changes
+
+- ce4b213: fix(providers): normalize string tool-call arguments across all providers
+
+ Models occasionally emit tool-call arguments as a JSON string instead of an
+ object (most visibly with `COMPOSIO_MULTI_EXECUTE_TOOL` on the Vercel AI SDK),
+ which broke downstream validation with errors like
+ `tool_use.input: Input should be a valid dictionary`.
+
+ `@composio/core` now exposes a single `normalizeToolArguments` helper, and every
+ provider routes model-supplied arguments through it. Object payloads pass
+ through unchanged, JSON strings are parsed, empty/`null` payloads become `{}`,
+ and anything that cannot resolve to an object throws a typed
+ `ComposioInvalidToolArgumentsError` instead of a raw `SyntaxError` or a silently
+ forwarded malformed string. This replaces the inconsistent per-provider guards
+ that previously existed only in vercel, cloudflare and openai-agents.
+
## 0.9.2
### Patch Changes
diff --git a/ts/packages/providers/vercel/package.json b/ts/packages/providers/vercel/package.json
index 463be3768..1cb10d484 100644
--- a/ts/packages/providers/vercel/package.json
+++ b/ts/packages/providers/vercel/package.json
@@ -1,6 +1,6 @@
{
"name": "@composio/vercel",
- "version": "0.9.2",
+ "version": "0.9.3",
"description": "",
"main": "src/index.ts",
"publishConfig": {