Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
TypeScript agentic-aiagentsaiai-agentsaiagentsdeveloper-toolsfunction-callinggpt-4javascriptjsllmllmopsmcppythonremote-mcp-serverssetypescript
Release: update version (#3616)
sdkrelease[bot]9764ce33ff63
diff --git a/.changeset/anthropic-sanitize-keys-hardening.md b/.changeset/anthropic-sanitize-keys-hardening.mddeleted file mode 100644index 67a37653f..000000000--- a/.changeset/anthropic-sanitize-keys-hardening.md+++ /dev/null@@ -1,14 +0,0 @@-----'@composio/anthropic': patch------Harden the Anthropic tool property-key sanitizer:--- **Broader schema coverage.** Illegal keys are now sanitized wherever they appear in a tool schema — under the composition keywords (`allOf`/`anyOf`/`oneOf`, `not`/`if`/`then`/`else`), `prefixItems` tuples, `additionalProperties`/`patternProperties`, and `$defs`/`definitions` — not just top-level `properties` and array `items`. Previously a single illegal key under one of these would still 400 the entire request. Renames inside composition keywords are restored correctly (they fold into the value level they share).-- **`$ref` keys restored.** `wrapTool` now dereferences internal `$ref`/`$defs` (leniently — a dangling ref degrades to a permissive schema instead of throwing) before sanitizing, so keys reachable only through a reference are both made compliant and restored. Only genuinely dynamic positions (`additionalProperties`, `patternProperties`, `contains`) remain rewrite-only.-- **Shared core implementation.** The traversal/restoration mechanism now lives in `@composio/core` (`sanitizeSchemaPropertyKeys` / `restoreOriginalKeys`); this provider supplies only the Anthropic key constraint as a policy, reusing core's prototype-pollution guard and depth cap.-- **Prototype-safe key restoration.** Reverse-mapping lookups and the rebuilt argument object are now prototype-free, so a tool call whose arguments use a key matching an `Object.prototype` member (`__proto__`, `constructor`, `toString`, `hasOwnProperty`, …) no longer throws or silently corrupts the payload sent to the backend. `Object.prototype` is never mutated.-- **Depth cap.** Schema sanitization and key restoration now bound recursion (matching core's JSON-schema walker) so a pathologically deep schema or argument object fails with a clear error instead of overflowing the stack.-- **Empty / all-illegal keys.** A property key that is empty (or made entirely of stripped characters) now becomes a deterministic non-empty alias instead of an empty string, which would itself have violated Anthropic's `{1,64}` length bound.-- **Collision loop.** Replaced a latent non-terminating fixed point in the alias collision resolver with a counter that always makes progress.-- **Observability.** The provider now emits `debug` logs when it rewrites a tool's schema keys and when it restores them at execution time, and the wrap-then-execute (same provider instance) contract for key restoration is documented.diff --git a/.changeset/anthropic-sanitize-tool-property-keys.md b/.changeset/anthropic-sanitize-tool-property-keys.mddeleted file mode 100644index 1b7858b77..000000000--- a/.changeset/anthropic-sanitize-tool-property-keys.md+++ /dev/null@@ -1,7 +0,0 @@-----'@composio/anthropic': patch------Sanitize tool `input_schema` property keys that violate Anthropic's `^[a-zA-Z0-9_.-]{1,64}$` constraint before sending tools to the Messages API, then restore the original names when the tool is executed.--A single non-conforming key previously made Anthropic reject the entire `tools` array with HTTP 400, taking down every other tool in the same request. This commonly happened with OneDrive's Microsoft Graph OData parameters (`$top`, `$filter`, `@microsoft.graph.conflictBehavior`) and with over-long flattened keys from tools such as Zoom. Offending keys are now rewritten to conforming aliases (`$` → `dollar_`, `@` → `at_`, any other illegal character → `_`, keys longer than 64 characters truncated with a deterministic suffix), recursing through nested object `properties` and array `items` schemas. The original parameter names are restored before the call reaches the Composio backend, so the model sees `dollar_top` while the backend still receives `$top`. Schemas whose keys already conform are left unchanged.diff --git a/.changeset/auth-config-list-search.md b/.changeset/auth-config-list-search.mddeleted file mode 100644index 015d5510b..000000000--- a/.changeset/auth-config-list-search.md+++ /dev/null@@ -1,5 +0,0 @@-----'@composio/core': patch------Expose `search` and `showDisabled` filters on `authConfigs.list()`.diff --git a/.changeset/bump-composio-client-alpha74.md b/.changeset/bump-composio-client-alpha74.mddeleted file mode 100644index 645db442d..000000000--- a/.changeset/bump-composio-client-alpha74.md+++ /dev/null@@ -1,6 +0,0 @@-----'@composio/core': minor-'@composio/cli': minor------Bump `@composio/client` to `0.1.0-alpha.74`.diff --git a/.changeset/cli-drop-recipe-meta-tool-slugs.md b/.changeset/cli-drop-recipe-meta-tool-slugs.mddeleted file mode 100644index 52af453fc..000000000--- a/.changeset/cli-drop-recipe-meta-tool-slugs.md+++ /dev/null@@ -1,5 +0,0 @@-----'@composio/cli': patch------Drop `COMPOSIO_UPSERT_RECIPE` and `COMPOSIO_GET_RECIPE` from the CLI meta-tool list. These slugs were removed from `@composio/client` (alpha.74), so listing them broke the type-checked CLI build.diff --git a/.changeset/cli-remove-unused-ansis.md b/.changeset/cli-remove-unused-ansis.mddeleted file mode 100644index dfe921cca..000000000--- a/.changeset/cli-remove-unused-ansis.md+++ /dev/null@@ -1,5 +0,0 @@-----'@composio/cli': patch------Remove the unused `ansis` dependency from the CLI. Colored output is already handled by `picocolors`, so `ansis` was a dead production dependency that shipped with the package.diff --git a/.changeset/core-chalk-to-picocolors.md b/.changeset/core-chalk-to-picocolors.mddeleted file mode 100644index 01b7bcd39..000000000--- a/.changeset/core-chalk-to-picocolors.md+++ /dev/null@@ -1,5 +0,0 @@-----'@composio/core': patch------Replace `chalk` with `picocolors` for colored error and log output. The two render identically, but `picocolors` is a fraction of the size (~0.8 kB gzipped vs chalk's much larger footprint), shrinking the bundled package.diff --git a/.changeset/core-request-options-signal-timeout.md b/.changeset/core-request-options-signal-timeout.mddeleted file mode 100644index 4a0df6596..000000000--- a/.changeset/core-request-options-signal-timeout.md+++ /dev/null@@ -1,57 +0,0 @@-----"@composio/core": minor------Add per-request cancellation to public SDK methods via a new `ComposioRequestOptions` (`{ signal?: AbortSignal }`) trailing argument, plus a typed `ComposioRequestCancelledError` for detecting caller-initiated aborts.--Without this, a slow `tools.get` or `tools.execute` had no way to be cancelled — a 100s search would block the calling agent indefinitely. The new shape:--```typescript-try {- const tools = await composio.tools.get(- 'user_1',- { search: 'send email', limit: 50 },- { signal: AbortSignal.timeout(5_000) }- );-} catch (err) {- if (err instanceof ComposioRequestCancelledError) {- return;- }- throw err;-}-```--The signal is forwarded to the underlying `@composio/client` fetch. Any abort error (`APIUserAbortError`, `AbortError`, or `DOMException(name='AbortError')`) coming back is normalized to `ComposioRequestCancelledError` so callers can `instanceof`-detect cancellation without unwrapping nested causes. Catch-and-wrap paths in `tools.execute` / `tools.getRawComposioToolBySlug` / `toolkits.get` re-throw the cancellation error rather than remapping it to `ComposioToolExecutionError` / `ComposioToolNotFoundError` / `ComposioToolkitFetchError`.--Wired through on:-- **Tools**: `get`, `getRawComposioTools`, `getRawComposioToolBySlug`, `getRawToolRouterSessionTools`, `execute`, `executeSessionTool`, `getToolsEnum`, `getInput`, `proxyExecute`-- **Toolkits**: `get`, `listCategories`-- **AuthConfigs**: `list`, `create`, `get`, `update`, `delete`, `updateStatus`, `enable`, `disable`-- **ConnectedAccounts**: `list`, `get`, `delete`, `refresh`, `updateStatus`, `enable`, `disable`, `update`-- **Triggers**: `listActive`, `create`, `update`, `delete`, `enable`, `disable`, `listTypes`, `getType`, `listEnum`-- **MCP**: `create`, `list`, `get`, `delete`, `update`, `generate`-- **ToolRouter** (`composio.create` / `composio.use`, `composio.toolRouter.create` / `.use`) — long-running session-creation paths-- **ToolRouterSession**: `authorize`, `toolkits`, `search`, `execute`, `proxyExecute`, `update`--### Custom-tool cooperative cancellation--Native tool execution is cancelled by the SDK (the underlying `fetch` is aborted). Custom tools are different — the SDK can't preempt user-supplied JavaScript. Two affordances are added so callers get sensible behavior anyway:--1. **Pre-execute signal check**: if `signal.aborted` is true before the user's `execute` runs, the SDK throws `ComposioRequestCancelledError` and never invokes user code.-2. **Cooperative signal forwarding**: the same `AbortSignal` is exposed via `SessionContext.signal` for Tool Router custom tools. Long-running implementations can wire `ctx.signal` into their own `fetch` (or any abortable IO) to abort mid-execution; the resulting `AbortError` is normalized to `ComposioRequestCancelledError` by the SDK.--```typescript-import { experimental_createTool } from '@composio/core';--const longRunningFetch = experimental_createTool('LONG_RUNNING_FETCH', {- name: 'Long-running fetch',- description: 'Fetches a URL with cooperative cancellation',- inputParams: z.object({ url: z.string() }),- execute: async (input, ctx) => {- // Pass ctx.signal into fetch so a session.execute(...) abort cancels- // the in-flight HTTP request mid-flight.- const resp = await fetch(input.url, { signal: ctx.signal });- return { result: await resp.json() };- },-});-```diff --git a/.changeset/core-schema-property-key-sanitizer.md b/.changeset/core-schema-property-key-sanitizer.mddeleted file mode 100644index bebf58f0b..000000000--- a/.changeset/core-schema-property-key-sanitizer.md+++ /dev/null@@ -1,7 +0,0 @@-----'@composio/core': patch------Add a provider-agnostic JSON-schema property-key sanitizer: `sanitizeSchemaPropertyKeys(schema, policy)`, `restoreOriginalKeys(value, mapping)`, `mappingHasRenames(mapping)`, and the `KeyMapping` / `KeySanitizationPolicy` types.--Some providers constrain the characters and length of tool `input_schema` property keys and reject the whole request on a single violation. This utility rewrites offending keys to conforming aliases (recursing through `properties`, array `items`/`prefixItems`, the composition keywords `allOf`/`anyOf`/`oneOf` and `not`/`if`/`then`/`else`, plus `additionalProperties`/`patternProperties`/`$defs`/`contains`) and records a schema-shaped reverse mapping so the original parameter names can be restored before execution. The _constraint_ is injected as a `KeySanitizationPolicy`, so the traversal, collision handling, prototype safety, and depth cap stay provider-agnostic. The `@composio/anthropic` provider now consumes it.diff --git a/.changeset/drop-commonjs-entrypoints.md b/.changeset/drop-commonjs-entrypoints.mddeleted file mode 100644index 347f05ef4..000000000--- a/.changeset/drop-commonjs-entrypoints.md+++ /dev/null@@ -1,20 +0,0 @@-----'@composio/core': minor-'@composio/json-schema-to-zod': minor-'@composio/ts-builders': minor-'@composio/cli': minor-'@composio/cli-keyring': minor-'@composio/cli-local-tools': minor-'@composio/anthropic': minor-'@composio/claude-agent-sdk': minor-'@composio/cloudflare': minor-'@composio/google': minor-'@composio/langchain': minor-'@composio/llamaindex': minor-'@composio/mastra': minor-'@composio/openai': minor-'@composio/openai-agents': minor-'@composio/vercel': minor------Drop CommonJS entrypoints and publish the TypeScript SDK packages as ESM-only packages. This is a breaking change within the existing 0.x release line: consumers must use Node.js 22.22.3 or newer. CommonJS callers can only rely on Node's native `require(esm)` interop, and the SDK no longer ships custom CommonJS compatibility machinery or `.cjs` artifacts.diff --git a/.changeset/file-modifier-dereference-ref.md b/.changeset/file-modifier-dereference-ref.mddeleted file mode 100644index b4a7012a9..000000000--- a/.changeset/file-modifier-dereference-ref.md+++ /dev/null@@ -1,5 +0,0 @@-----'@composio/core': patch------Preserve root `$defs` / `definitions` blocks on tool parameter schemas and dereference them in the Node file modifier, so auto file upload/download detection works when `file_uploadable` or `file_downloadable` is hidden behind an internal `$ref`.diff --git a/.changeset/mastra-output-schema-nullable.md b/.changeset/mastra-output-schema-nullable.mddeleted file mode 100644index 0da4eda63..000000000--- a/.changeset/mastra-output-schema-nullable.md+++ /dev/null@@ -1,5 +0,0 @@-----'@composio/mastra': patch------Relax the Mastra provider output schema so real third-party API responses are no longer rejected by Mastra's output validation (which dropped the data and substituted an error). Before compilation the output schema is made lenient: every typed node becomes nullable, objects allow extra keys (`additionalProperties: true`), `enum`/`const` are widened to also admit `null`, and `required` is dropped (APIs omit unset fields rather than returning `null` for them). All of these only widen what validates, so previously-valid output is unaffected.diff --git a/.changeset/quiet-rules-cheer.md b/.changeset/quiet-rules-cheer.mddeleted file mode 100644index 45b59185f..000000000--- a/.changeset/quiet-rules-cheer.md+++ /dev/null@@ -1,9 +0,0 @@-----'@composio/core': minor------Remove the deprecated `uuid` field from the auth config retrieve/list response type.--The platform has removed the deprecated V1/V2 UUID-mirror field from V3 API responses (it was a mirror of the canonical nanoid `id`). The SDK no longer reads or re-exposes `uuid` on `AuthConfigRetrieveResponse` (and therefore on the items of `AuthConfigListResponse`).--This is technically a breaking change to the SDK response type: consumers should use `id` instead of `uuid`. The `expectedInputFields` field is unaffected — it remains a top-level field on the API response.diff --git a/.changeset/virtual-compiler-host-resolution.md b/.changeset/virtual-compiler-host-resolution.mddeleted file mode 100644index b03d90e7d..000000000--- a/.changeset/virtual-compiler-host-resolution.md+++ /dev/null@@ -1,5 +0,0 @@-----'@composio/cli': patch------Fix virtual TypeScript file resolution used by CLI type generation so in-memory imports resolve consistently during transpilation and validation.diff --git a/.changeset/zod-schema-compat.md b/.changeset/zod-schema-compat.mddeleted file mode 100644index c575224fe..000000000--- a/.changeset/zod-schema-compat.md+++ /dev/null@@ -1,6 +0,0 @@-----'@composio/core': patch-'@composio/claude-agent-sdk': patch------Improve Zod compatibility at the SDK schema boundary. Custom tools now convert both `zod/v3` and Zod v4 schemas to JSON Schema correctly instead of degrading Zod v4 object schemas to empty schemas. `@composio/core` now exposes `jsonSchemaToZodShape` via `@composio/core/utils/json-schema`, and the Claude Agent SDK provider uses that core subpath instead of converting to a full Zod object and casting `.shape` out of it.diff --git a/ts/packages/cli-keyring/CHANGELOG.md b/ts/packages/cli-keyring/CHANGELOG.mdnew file mode 100644index 000000000..5a0b15c8c--- /dev/null+++ b/ts/packages/cli-keyring/CHANGELOG.md@@ -0,0 +1,7 @@+# @composio/cli-keyring++## 0.2.0++### Minor Changes++- 025a657: Drop CommonJS entrypoints and publish the TypeScript SDK packages as ESM-only packages. This is a breaking change within the existing 0.x release line: consumers must use Node.js 22.22.3 or newer. CommonJS callers can only rely on Node's native `require(esm)` interop, and the SDK no longer ships custom CommonJS compatibility machinery or `.cjs` artifacts.diff --git a/ts/packages/cli-keyring/package.json b/ts/packages/cli-keyring/package.jsonindex 53ab07486..035edae5e 100644--- a/ts/packages/cli-keyring/package.json+++ b/ts/packages/cli-keyring/package.json@@ -1,6 +1,6 @@{"name": "@composio/cli-keyring",- "version": "0.1.0",+ "version": "0.2.0","description": "Cross-platform OS credential store access for the Composio CLI (macOS Keychain, Linux Secret Service).","main": "src/index.ts","private": true,diff --git a/ts/packages/cli-local-tools/CHANGELOG.md b/ts/packages/cli-local-tools/CHANGELOG.mdindex 50f9a1e31..cf63b77b4 100644--- a/ts/packages/cli-local-tools/CHANGELOG.md+++ b/ts/packages/cli-local-tools/CHANGELOG.md@@ -1,5 +1,24 @@# @composio/cli-local-tools+## 0.1.0++### Minor Changes++- 025a657: Drop CommonJS entrypoints and publish the TypeScript SDK packages as ESM-only packages. This is a breaking change within the existing 0.x release line: consumers must use Node.js 22.22.3 or newer. CommonJS callers can only rely on Node's native `require(esm)` interop, and the SDK no longer ships custom CommonJS compatibility machinery or `.cjs` artifacts.++### Patch Changes++- Updated dependencies [552859a]+- Updated dependencies [a0bef5d]+- Updated dependencies [23f9053]+- Updated dependencies [dfd7a08]+- Updated dependencies [507318d]+- Updated dependencies [025a657]+- Updated dependencies [6a4cb54]+- Updated dependencies [4b76dbf]+- Updated dependencies [cbbad15]+ - @composio/[email protected]+## 0.0.5### Patch Changesdiff --git a/ts/packages/cli-local-tools/package.json b/ts/packages/cli-local-tools/package.jsonindex b46375279..38653efbd 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.5",+ "version": "0.1.0","private": true,"description": "Local tool and toolkit declarations for the Composio CLI.","type": "module",diff --git a/ts/packages/cli/CHANGELOG.md b/ts/packages/cli/CHANGELOG.mdindex 50edb91b6..8b1fafc84 100644--- a/ts/packages/cli/CHANGELOG.md+++ b/ts/packages/cli/CHANGELOG.md@@ -1,5 +1,32 @@# @composio/cli+## 0.3.0++### Minor Changes++- a0bef5d: Bump `@composio/client` to `0.1.0-alpha.74`.+- 025a657: Drop CommonJS entrypoints and publish the TypeScript SDK packages as ESM-only packages. This is a breaking change within the existing 0.x release line: consumers must use Node.js 22.22.3 or newer. CommonJS callers can only rely on Node's native `require(esm)` interop, and the SDK no longer ships custom CommonJS compatibility machinery or `.cjs` artifacts.++### Patch Changes++- 5f004ff: Drop `COMPOSIO_UPSERT_RECIPE` and `COMPOSIO_GET_RECIPE` from the CLI meta-tool list. These slugs were removed from `@composio/client` (alpha.74), so listing them broke the type-checked CLI build.+- 23f9053: Remove the unused `ansis` dependency from the CLI. Colored output is already handled by `picocolors`, so `ansis` was a dead production dependency that shipped with the package.+- 446c6f6: Fix virtual TypeScript file resolution used by CLI type generation so in-memory imports resolve consistently during transpilation and validation.+- Updated dependencies [552859a]+- Updated dependencies [a0bef5d]+- Updated dependencies [23f9053]+- Updated dependencies [dfd7a08]+- Updated dependencies [507318d]+- Updated dependencies [025a657]+- Updated dependencies [6a4cb54]+- Updated dependencies [4b76dbf]+- Updated dependencies [cbbad15]+ - @composio/[email protected]+ - @composio/[email protected]+ - @composio/[email protected]+ - @composio/[email protected]+ - @composio/[email protected]+## 0.2.32### Patch Changesdiff --git a/ts/packages/cli/package.json b/ts/packages/cli/package.jsonindex 8f0d42453..88789559a 100644--- a/ts/packages/cli/package.json+++ b/ts/packages/cli/package.json@@ -1,6 +1,6 @@{"name": "@composio/cli",- "version": "0.2.32",+ "version": "0.3.0","description": "Composio CLI","main": "./dist/bin.mjs","private": true,diff --git a/ts/packages/core/CHANGELOG.md b/ts/packages/core/CHANGELOG.mdindex 73e763fc0..e2a4dcf2f 100644--- a/ts/packages/core/CHANGELOG.md+++ b/ts/packages/core/CHANGELOG.md@@ -1,5 +1,84 @@# @composio/core+## 0.12.0++### Minor Changes++- a0bef5d: Bump `@composio/client` to `0.1.0-alpha.74`.+- dfd7a08: Add per-request cancellation to public SDK methods via a new `ComposioRequestOptions` (`{ signal?: AbortSignal }`) trailing argument, plus a typed `ComposioRequestCancelledError` for detecting caller-initiated aborts.++ Without this, a slow `tools.get` or `tools.execute` had no way to be cancelled — a 100s search would block the calling agent indefinitely. The new shape:++ ```typescript+ try {+ const tools = await composio.tools.get(+ 'user_1',+ { search: 'send email', limit: 50 },+ { signal: AbortSignal.timeout(5_000) }+ );+ } catch (err) {+ if (err instanceof ComposioRequestCancelledError) {+ return;+ }+ throw err;+ }+ ```++ The signal is forwarded to the underlying `@composio/client` fetch. Any abort error (`APIUserAbortError`, `AbortError`, or `DOMException(name='AbortError')`) coming back is normalized to `ComposioRequestCancelledError` so callers can `instanceof`-detect cancellation without unwrapping nested causes. Catch-and-wrap paths in `tools.execute` / `tools.getRawComposioToolBySlug` / `toolkits.get` re-throw the cancellation error rather than remapping it to `ComposioToolExecutionError` / `ComposioToolNotFoundError` / `ComposioToolkitFetchError`.++ Wired through on:+ - **Tools**: `get`, `getRawComposioTools`, `getRawComposioToolBySlug`, `getRawToolRouterSessionTools`, `execute`, `executeSessionTool`, `getToolsEnum`, `getInput`, `proxyExecute`+ - **Toolkits**: `get`, `listCategories`+ - **AuthConfigs**: `list`, `create`, `get`, `update`, `delete`, `updateStatus`, `enable`, `disable`+ - **ConnectedAccounts**: `list`, `get`, `delete`, `refresh`, `updateStatus`, `enable`, `disable`, `update`+ - **Triggers**: `listActive`, `create`, `update`, `delete`, `enable`, `disable`, `listTypes`, `getType`, `listEnum`+ - **MCP**: `create`, `list`, `get`, `delete`, `update`, `generate`+ - **ToolRouter** (`composio.create` / `composio.use`, `composio.toolRouter.create` / `.use`) — long-running session-creation paths+ - **ToolRouterSession**: `authorize`, `toolkits`, `search`, `execute`, `proxyExecute`, `update`++ ### Custom-tool cooperative cancellation++ Native tool execution is cancelled by the SDK (the underlying `fetch` is aborted). Custom tools are different — the SDK can't preempt user-supplied JavaScript. Two affordances are added so callers get sensible behavior anyway:++ 1. **Pre-execute signal check**: if `signal.aborted` is true before the user's `execute` runs, the SDK throws `ComposioRequestCancelledError` and never invokes user code.+ 2. **Cooperative signal forwarding**: the same `AbortSignal` is exposed via `SessionContext.signal` for Tool Router custom tools. Long-running implementations can wire `ctx.signal` into their own `fetch` (or any abortable IO) to abort mid-execution; the resulting `AbortError` is normalized to `ComposioRequestCancelledError` by the SDK.++ ```typescript+ import { experimental_createTool } from '@composio/core';++ const longRunningFetch = experimental_createTool('LONG_RUNNING_FETCH', {+ name: 'Long-running fetch',+ description: 'Fetches a URL with cooperative cancellation',+ inputParams: z.object({ url: z.string() }),+ execute: async (input, ctx) => {+ // Pass ctx.signal into fetch so a session.execute(...) abort cancels+ // the in-flight HTTP request mid-flight.+ const resp = await fetch(input.url, { signal: ctx.signal });+ return { result: await resp.json() };+ },+ });+ ```++- 025a657: Drop CommonJS entrypoints and publish the TypeScript SDK packages as ESM-only packages. This is a breaking change within the existing 0.x release line: consumers must use Node.js 22.22.3 or newer. CommonJS callers can only rely on Node's native `require(esm)` interop, and the SDK no longer ships custom CommonJS compatibility machinery or `.cjs` artifacts.+- 4b76dbf: Remove the deprecated `uuid` field from the auth config retrieve/list response type.++ The platform has removed the deprecated V1/V2 UUID-mirror field from V3 API responses (it was a mirror of the canonical nanoid `id`). The SDK no longer reads or re-exposes `uuid` on `AuthConfigRetrieveResponse` (and therefore on the items of `AuthConfigListResponse`).++ This is technically a breaking change to the SDK response type: consumers should use `id` instead of `uuid`. The `expectedInputFields` field is unaffected — it remains a top-level field on the API response.++### Patch Changes++- 552859a: Expose `search` and `showDisabled` filters on `authConfigs.list()`.+- 23f9053: Replace `chalk` with `picocolors` for colored error and log output. The two render identically, but `picocolors` is a fraction of the size (~0.8 kB gzipped vs chalk's much larger footprint), shrinking the bundled package.+- 507318d: Add a provider-agnostic JSON-schema property-key sanitizer: `sanitizeSchemaPropertyKeys(schema, policy)`, `restoreOriginalKeys(value, mapping)`, `mappingHasRenames(mapping)`, and the `KeyMapping` / `KeySanitizationPolicy` types.++ Some providers constrain the characters and length of tool `input_schema` property keys and reject the whole request on a single violation. This utility rewrites offending keys to conforming aliases (recursing through `properties`, array `items`/`prefixItems`, the composition keywords `allOf`/`anyOf`/`oneOf` and `not`/`if`/`then`/`else`, plus `additionalProperties`/`patternProperties`/`$defs`/`contains`) and records a schema-shaped reverse mapping so the original parameter names can be restored before execution. The _constraint_ is injected as a `KeySanitizationPolicy`, so the traversal, collision handling, prototype safety, and depth cap stay provider-agnostic. The `@composio/anthropic` provider now consumes it.++- 6a4cb54: Preserve root `$defs` / `definitions` blocks on tool parameter schemas and dereference them in the Node file modifier, so auto file upload/download detection works when `file_uploadable` or `file_downloadable` is hidden behind an internal `$ref`.+- cbbad15: Improve Zod compatibility at the SDK schema boundary. Custom tools now convert both `zod/v3` and Zod v4 schemas to JSON Schema correctly instead of degrading Zod v4 object schemas to empty schemas. `@composio/core` now exposes `jsonSchemaToZodShape` via `@composio/core/utils/json-schema`, and the Claude Agent SDK provider uses that core subpath instead of converting to a full Zod object and casting `.shape` out of it.+- Updated dependencies [025a657]+ - @composio/[email protected]+## 0.11.0### Minor Changesdiff --git a/ts/packages/core/package.json b/ts/packages/core/package.jsonindex 8be257b97..b0de574a9 100644--- a/ts/packages/core/package.json+++ b/ts/packages/core/package.json@@ -1,7 +1,7 @@{"name": "@composio/core","type": "module",- "version": "0.11.0",+ "version": "0.12.0","description": "","main": "src/index.ts","publishConfig": {diff --git a/ts/packages/json-schema-to-zod/CHANGELOG.md b/ts/packages/json-schema-to-zod/CHANGELOG.mdindex 75df8ac79..8f534348a 100644--- a/ts/packages/json-schema-to-zod/CHANGELOG.md+++ b/ts/packages/json-schema-to-zod/CHANGELOG.md@@ -1,5 +1,11 @@# @composio/json-schema-to-zod+## 0.2.0++### Minor Changes++- 025a657: Drop CommonJS entrypoints and publish the TypeScript SDK packages as ESM-only packages. This is a breaking change within the existing 0.x release line: consumers must use Node.js 22.22.3 or newer. CommonJS callers can only rely on Node's native `require(esm)` interop, and the SDK no longer ships custom CommonJS compatibility machinery or `.cjs` artifacts.+## 0.1.20### Patch Changesdiff --git a/ts/packages/json-schema-to-zod/package.json b/ts/packages/json-schema-to-zod/package.jsonindex 78fd96ebd..bac5e33ea 100644--- a/ts/packages/json-schema-to-zod/package.json+++ b/ts/packages/json-schema-to-zod/package.json@@ -1,6 +1,6 @@{"name": "@composio/json-schema-to-zod",- "version": "0.1.20",+ "version": "0.2.0","description": "","main": "src/index.ts","type": "module",diff --git a/ts/packages/providers/anthropic/CHANGELOG.md b/ts/packages/providers/anthropic/CHANGELOG.mdindex fedc102ac..5501f99ae 100644--- a/ts/packages/providers/anthropic/CHANGELOG.md+++ b/ts/packages/providers/anthropic/CHANGELOG.md@@ -1,5 +1,28 @@# @composio/anthropic+## 0.10.0++### Minor Changes++- 025a657: Drop CommonJS entrypoints and publish the TypeScript SDK packages as ESM-only packages. This is a breaking change within the existing 0.x release line: consumers must use Node.js 22.22.3 or newer. CommonJS callers can only rely on Node's native `require(esm)` interop, and the SDK no longer ships custom CommonJS compatibility machinery or `.cjs` artifacts.++### Patch Changes++- 507318d: Harden the Anthropic tool property-key sanitizer:++ - **Broader schema coverage.** Illegal keys are now sanitized wherever they appear in a tool schema — under the composition keywords (`allOf`/`anyOf`/`oneOf`, `not`/`if`/`then`/`else`), `prefixItems` tuples, `additionalProperties`/`patternProperties`, and `$defs`/`definitions` — not just top-level `properties` and array `items`. Previously a single illegal key under one of these would still 400 the entire request. Renames inside composition keywords are restored correctly (they fold into the value level they share).+ - **`$ref` keys restored.** `wrapTool` now dereferences internal `$ref`/`$defs` (leniently — a dangling ref degrades to a permissive schema instead of throwing) before sanitizing, so keys reachable only through a reference are both made compliant and restored. Only genuinely dynamic positions (`additionalProperties`, `patternProperties`, `contains`) remain rewrite-only.+ - **Shared core implementation.** The traversal/restoration mechanism now lives in `@composio/core` (`sanitizeSchemaPropertyKeys` / `restoreOriginalKeys`); this provider supplies only the Anthropic key constraint as a policy, reusing core's prototype-pollution guard and depth cap.+ - **Prototype-safe key restoration.** Reverse-mapping lookups and the rebuilt argument object are now prototype-free, so a tool call whose arguments use a key matching an `Object.prototype` member (`__proto__`, `constructor`, `toString`, `hasOwnProperty`, …) no longer throws or silently corrupts the payload sent to the backend. `Object.prototype` is never mutated.+ - **Depth cap.** Schema sanitization and key restoration now bound recursion (matching core's JSON-schema walker) so a pathologically deep schema or argument object fails with a clear error instead of overflowing the stack.+ - **Empty / all-illegal keys.** A property key that is empty (or made entirely of stripped characters) now becomes a deterministic non-empty alias instead of an empty string, which would itself have violated Anthropic's `{1,64}` length bound.+ - **Collision loop.** Replaced a latent non-terminating fixed point in the alias collision resolver with a counter that always makes progress.+ - **Observability.** The provider now emits `debug` logs when it rewrites a tool's schema keys and when it restores them at execution time, and the wrap-then-execute (same provider instance) contract for key restoration is documented.++- c90ae95: Sanitize tool `input_schema` property keys that violate Anthropic's `^[a-zA-Z0-9_.-]{1,64}$` constraint before sending tools to the Messages API, then restore the original names when the tool is executed.++ A single non-conforming key previously made Anthropic reject the entire `tools` array with HTTP 400, taking down every other tool in the same request. This commonly happened with OneDrive's Microsoft Graph OData parameters (`$top`, `$filter`, `@microsoft.graph.conflictBehavior`) and with over-long flattened keys from tools such as Zoom. Offending keys are now rewritten to conforming aliases (`$` → `dollar_`, `@` → `at_`, any other illegal character → `_`, keys longer than 64 characters truncated with a deterministic suffix), recursing through nested object `properties` and array `items` schemas. The original parameter names are restored before the call reaches the Composio backend, so the model sees `dollar_top` while the backend still receives `$top`. Schemas whose keys already conform are left unchanged.+## 0.9.3### Patch Changesdiff --git a/ts/packages/providers/anthropic/package.json b/ts/packages/providers/anthropic/package.jsonindex 9eb905214..2a70ae132 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.3",+ "version": "0.10.0","description": "Non-Agentic Provider for Anthropic in Composio SDK","main": "src/index.ts","type": "module",diff --git a/ts/packages/providers/claude-agent-sdk/CHANGELOG.md b/ts/packages/providers/claude-agent-sdk/CHANGELOG.mdindex ec840159c..00273d84b 100644--- a/ts/packages/providers/claude-agent-sdk/CHANGELOG.md+++ b/ts/packages/providers/claude-agent-sdk/CHANGELOG.md@@ -1,5 +1,15 @@# @composio/claude-code-agents+## 0.10.0++### Minor Changes++- 025a657: Drop CommonJS entrypoints and publish the TypeScript SDK packages as ESM-only packages. This is a breaking change within the existing 0.x release line: consumers must use Node.js 22.22.3 or newer. CommonJS callers can only rely on Node's native `require(esm)` interop, and the SDK no longer ships custom CommonJS compatibility machinery or `.cjs` artifacts.++### Patch Changes++- cbbad15: Improve Zod compatibility at the SDK schema boundary. Custom tools now convert both `zod/v3` and Zod v4 schemas to JSON Schema correctly instead of degrading Zod v4 object schemas to empty schemas. `@composio/core` now exposes `jsonSchemaToZodShape` via `@composio/core/utils/json-schema`, and the Claude Agent SDK provider uses that core subpath instead of converting to a full Zod object and casting `.shape` out of it.+## 0.9.3### Patch Changesdiff --git a/ts/packages/providers/claude-agent-sdk/package.json b/ts/packages/providers/claude-agent-sdk/package.jsonindex 945536c0e..8ca375ba4 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.3",+ "version": "0.10.0","description": "Composio provider for Claude Agent SDK","main": "src/index.ts","type": "module",diff --git a/ts/packages/providers/cloudflare/CHANGELOG.md b/ts/packages/providers/cloudflare/CHANGELOG.mdindex 30a0a298c..eb24a628b 100644--- a/ts/packages/providers/cloudflare/CHANGELOG.md+++ b/ts/packages/providers/cloudflare/CHANGELOG.md@@ -1,5 +1,11 @@# @composio/cloudflare+## 0.10.0++### Minor Changes++- 025a657: Drop CommonJS entrypoints and publish the TypeScript SDK packages as ESM-only packages. This is a breaking change within the existing 0.x release line: consumers must use Node.js 22.22.3 or newer. CommonJS callers can only rely on Node's native `require(esm)` interop, and the SDK no longer ships custom CommonJS compatibility machinery or `.cjs` artifacts.+## 0.9.3### Patch Changesdiff --git a/ts/packages/providers/cloudflare/package.json b/ts/packages/providers/cloudflare/package.jsonindex 1868da6e4..5d6402b5f 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.3",+ "version": "0.10.0","description": "","main": "src/index.ts","type": "module",diff --git a/ts/packages/providers/google/CHANGELOG.md b/ts/packages/providers/google/CHANGELOG.mdindex 70901308f..ba8a17c3c 100644--- a/ts/packages/providers/google/CHANGELOG.md+++ b/ts/packages/providers/google/CHANGELOG.md@@ -1,5 +1,11 @@# @composio/google+## 0.10.0++### Minor Changes++- 025a657: Drop CommonJS entrypoints and publish the TypeScript SDK packages as ESM-only packages. This is a breaking change within the existing 0.x release line: consumers must use Node.js 22.22.3 or newer. CommonJS callers can only rely on Node's native `require(esm)` interop, and the SDK no longer ships custom CommonJS compatibility machinery or `.cjs` artifacts.+## 0.9.3### Patch Changesdiff --git a/ts/packages/providers/google/package.json b/ts/packages/providers/google/package.jsonindex 137b197a7..a1db282af 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.3",+ "version": "0.10.0","description": "Google GenAI Provider for Composio SDK","main": "src/index.ts","type": "module",diff --git a/ts/packages/providers/langchain/CHANGELOG.md b/ts/packages/providers/langchain/CHANGELOG.mdindex 18b2bcd25..5bd1c4858 100644--- a/ts/packages/providers/langchain/CHANGELOG.md+++ b/ts/packages/providers/langchain/CHANGELOG.md@@ -1,5 +1,11 @@# @composio/langchain+## 0.10.0++### Minor Changes++- 025a657: Drop CommonJS entrypoints and publish the TypeScript SDK packages as ESM-only packages. This is a breaking change within the existing 0.x release line: consumers must use Node.js 22.22.3 or newer. CommonJS callers can only rely on Node's native `require(esm)` interop, and the SDK no longer ships custom CommonJS compatibility machinery or `.cjs` artifacts.+## 0.9.3### Patch Changesdiff --git a/ts/packages/providers/langchain/package.json b/ts/packages/providers/langchain/package.jsonindex 41828d696..66cd024ff 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.3",+ "version": "0.10.0","description": "","main": "dist/index.js","type": "module",diff --git a/ts/packages/providers/llamaindex/CHANGELOG.md b/ts/packages/providers/llamaindex/CHANGELOG.mdindex 0a0f1771b..bf83dc6df 100644--- a/ts/packages/providers/llamaindex/CHANGELOG.md+++ b/ts/packages/providers/llamaindex/CHANGELOG.md@@ -1,5 +1,11 @@# @composio/llamaindex+## 0.10.0++### Minor Changes++- 025a657: Drop CommonJS entrypoints and publish the TypeScript SDK packages as ESM-only packages. This is a breaking change within the existing 0.x release line: consumers must use Node.js 22.22.3 or newer. CommonJS callers can only rely on Node's native `require(esm)` interop, and the SDK no longer ships custom CommonJS compatibility machinery or `.cjs` artifacts.+## 0.9.3### Patch Changesdiff --git a/ts/packages/providers/llamaindex/package.json b/ts/packages/providers/llamaindex/package.jsonindex ece2e5140..d606be2b6 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.3",+ "version": "0.10.0","description": "Agentic Provider for llamaindex in Composio SDK","main": "src/index.ts","type": "module",diff --git a/ts/packages/providers/mastra/CHANGELOG.md b/ts/packages/providers/mastra/CHANGELOG.mdindex 101a3f3f3..c17268121 100644--- a/ts/packages/providers/mastra/CHANGELOG.md+++ b/ts/packages/providers/mastra/CHANGELOG.md@@ -1,5 +1,15 @@# @composio/mastra+## 0.10.0++### Minor Changes++- 025a657: Drop CommonJS entrypoints and publish the TypeScript SDK packages as ESM-only packages. This is a breaking change within the existing 0.x release line: consumers must use Node.js 22.22.3 or newer. CommonJS callers can only rely on Node's native `require(esm)` interop, and the SDK no longer ships custom CommonJS compatibility machinery or `.cjs` artifacts.++### Patch Changes++- aaabf5e: Relax the Mastra provider output schema so real third-party API responses are no longer rejected by Mastra's output validation (which dropped the data and substituted an error). Before compilation the output schema is made lenient: every typed node becomes nullable, objects allow extra keys (`additionalProperties: true`), `enum`/`const` are widened to also admit `null`, and `required` is dropped (APIs omit unset fields rather than returning `null` for them). All of these only widen what validates, so previously-valid output is unaffected.+## 0.9.3### Patch Changesdiff --git a/ts/packages/providers/mastra/package.json b/ts/packages/providers/mastra/package.jsonindex fb27b6b8e..ea8e6aaa4 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.3",+ "version": "0.10.0","description": "Agentic Provider for mastra in Composio SDK","main": "src/index.ts","type": "module",diff --git a/ts/packages/providers/openai-agents/CHANGELOG.md b/ts/packages/providers/openai-agents/CHANGELOG.mdindex 704b5b4e4..f79007ab0 100644--- a/ts/packages/providers/openai-agents/CHANGELOG.md+++ b/ts/packages/providers/openai-agents/CHANGELOG.md@@ -1,5 +1,11 @@# @composio/openai-agents+## 0.10.0++### Minor Changes++- 025a657: Drop CommonJS entrypoints and publish the TypeScript SDK packages as ESM-only packages. This is a breaking change within the existing 0.x release line: consumers must use Node.js 22.22.3 or newer. CommonJS callers can only rely on Node's native `require(esm)` interop, and the SDK no longer ships custom CommonJS compatibility machinery or `.cjs` artifacts.+## 0.9.3### Patch Changesdiff --git a/ts/packages/providers/openai-agents/package.json b/ts/packages/providers/openai-agents/package.jsonindex aacb443bb..5ecd541b1 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.3",+ "version": "0.10.0","description": "","main": "src/index.ts","type": "module",diff --git a/ts/packages/providers/openai/CHANGELOG.md b/ts/packages/providers/openai/CHANGELOG.mdindex 87644bed4..57a1b3f20 100644--- a/ts/packages/providers/openai/CHANGELOG.md+++ b/ts/packages/providers/openai/CHANGELOG.md@@ -1,5 +1,11 @@# @composio/openai+## 0.10.0++### Minor Changes++- 025a657: Drop CommonJS entrypoints and publish the TypeScript SDK packages as ESM-only packages. This is a breaking change within the existing 0.x release line: consumers must use Node.js 22.22.3 or newer. CommonJS callers can only rely on Node's native `require(esm)` interop, and the SDK no longer ships custom CommonJS compatibility machinery or `.cjs` artifacts.+## 0.9.3### Patch Changesdiff --git a/ts/packages/providers/openai/package.json b/ts/packages/providers/openai/package.jsonindex ffe5fc670..fbd41a26b 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.3",+ "version": "0.10.0","description": "","main": "src/index.ts","type": "module",diff --git a/ts/packages/providers/vercel/CHANGELOG.md b/ts/packages/providers/vercel/CHANGELOG.mdindex f06f08c5a..084302a64 100644--- a/ts/packages/providers/vercel/CHANGELOG.md+++ b/ts/packages/providers/vercel/CHANGELOG.md@@ -1,5 +1,11 @@# @composio/vercel+## 0.10.0++### Minor Changes++- 025a657: Drop CommonJS entrypoints and publish the TypeScript SDK packages as ESM-only packages. This is a breaking change within the existing 0.x release line: consumers must use Node.js 22.22.3 or newer. CommonJS callers can only rely on Node's native `require(esm)` interop, and the SDK no longer ships custom CommonJS compatibility machinery or `.cjs` artifacts.+## 0.9.3### Patch Changesdiff --git a/ts/packages/providers/vercel/package.json b/ts/packages/providers/vercel/package.jsonindex 3e433e18b..ae5ddf4c6 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.3",+ "version": "0.10.0","description": "","main": "src/index.ts","type": "module",diff --git a/ts/packages/ts-builders/CHANGELOG.md b/ts/packages/ts-builders/CHANGELOG.mdnew file mode 100644index 000000000..33ea495b8--- /dev/null+++ b/ts/packages/ts-builders/CHANGELOG.md@@ -0,0 +1,7 @@+# @composio/ts-builders++## 0.2.0++### Minor Changes++- 025a657: Drop CommonJS entrypoints and publish the TypeScript SDK packages as ESM-only packages. This is a breaking change within the existing 0.x release line: consumers must use Node.js 22.22.3 or newer. CommonJS callers can only rely on Node's native `require(esm)` interop, and the SDK no longer ships custom CommonJS compatibility machinery or `.cjs` artifacts.diff --git a/ts/packages/ts-builders/package.json b/ts/packages/ts-builders/package.jsonindex 1a0951a59..b7e714b5c 100644--- a/ts/packages/ts-builders/package.json+++ b/ts/packages/ts-builders/package.json@@ -1,6 +1,6 @@{"name": "@composio/ts-builders",- "version": "0.1.24",+ "version": "0.2.0","description": "Fork of @prisma/ts-builders","main": "dist/index.mjs","type": "module",