Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
| 1 | --- |
| 2 | title: 'TypeScript SDK 0.14.0 hardens file uploads and tool execution' |
| 3 | description: 'TypeScript SDK 0.14.0 blocks unsafe URL uploads, redacts secrets from telemetry, and makes tool execution more reliable.' |
| 4 | date: '2026-07-15' |
| 5 | --- |
| 6 | |
| 7 | TypeScript SDK `@composio/core` `0.14.0` closes file-upload and telemetry exposure paths, prevents duplicate tool side effects after retries, and aligns trigger creation with backend connection resolution. |
| 8 | |
| 9 | ### SDK versions |
| 10 | |
| 11 | | SDK | Version | |
| 12 | | --------------------------- | -------- | |
| 13 | | TypeScript `@composio/core` | `0.14.0` | |
| 14 | |
| 15 | ### File and telemetry security |
| 16 | |
| 17 | - URL file uploads and automatic uploads during tool execution reject private, loopback, link-local, carrier-grade NAT, and reserved addresses. Redirects are checked at every hop, and blocked requests raise `ComposioBlockedInternalUrlError`. |
| 18 | - Error telemetry redacts URL query strings, authorization credentials, and secret-like key-value pairs before transport. |
| 19 | - The package root exports `assertSafeFileUploadPath`, `isBlockedSensitiveFileUploadPath`, and `BUILTIN_FILE_UPLOAD_PATH_DENY_SEGMENTS` so downstream packages can apply the same sensitive-file denylist. |
| 20 | |
| 21 | ### Tool execution reliability |
| 22 | |
| 23 | - `tools.execute()` and `tools.proxyExecute()` no longer retry non-idempotent writes, preventing a timeout from repeating side effects such as sending the same email twice. |
| 24 | - `OpenAIProvider.handleToolCalls()` executes every tool call from the first assistant choice and returns one result for each `tool_call_id` in deterministic order. |
| 25 | - Provider tool schemas normalize duplicate JSON Schema `required` entries before they are emitted. |
| 26 | |
| 27 | ### Trigger and toolkit behavior |
| 28 | |
| 29 | `triggers.create()` now sends `user_id` directly to the backend when `connectedAccountId` is omitted. This removes the extra connected-account lookup and lets the backend select the first active connection for the user and toolkit. |
| 30 | |
| 31 | <Callout type="warn"> |
| 32 | **Behavior change** |
| 33 | |
| 34 | A missing or invalid connection now surfaces the backend upsert error instead of `ComposioConnectedAccountNotFoundError`. Self-hosted deployments need a backend version that resolves trigger connections from `user_id`. |
| 35 | |
| 36 | </Callout> |
| 37 | |
| 38 | Toolkit version pins are also case-insensitive in configuration objects and environment variables, so casing differences no longer fall back silently to `latest`. |