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

next
mdx 56 lines 1.99 KB
Raw
1 ---
2 title: "TypeScript SDK 0.11.0 moves custom tools to Tool Router"
3 description: "TypeScript SDK 0.11.0 removes the legacy custom-tool registry and improves trigger ownership, schemas, file handling, and provider tool arguments."
4 date: "2026-06-19"
5 ---
6
7 TypeScript SDK `@composio/core` `0.11.0` removes the old in-memory custom-tool registry. Custom tools now have one home: Tool Router sessions.
8
9 ### SDK versions
10
11 | SDK | Version |
12 | --- | --- |
13 | TypeScript `@composio/core` | `0.11.0` |
14
15 ### Breaking change
16
17 <Callout type="warn">
18 **Breaking change**
19
20 `composio.tools.createCustomTool(...)` was removed. Because the SDK is still pre-1.0, this shipped as a minor release. Existing `^0.10.0` ranges do not upgrade to `0.11.0` automatically.
21 </Callout>
22
23 **Before:**
24
25 ```typescript
26 // @noErrors
27 const tool = composio.tools.createCustomTool({ /* ... */ });
28 ```
29
30 **After:**
31
32 ```typescript
33 // @noErrors
34 import { experimental_createTool } from '@composio/core';
35
36 const tool = experimental_createTool('GREP', {
37 name: 'Grep Search',
38 description: 'Search local files',
39 inputParams: /* zod schema */,
40 execute: async (input) => ({ input }),
41 });
42
43 await composio.create('user_123', {
44 experimental: { customTools: [tool] },
45 });
46 ```
47
48 Use `experimental_createToolkit(...)` when several local tools belong together. The `experimental_*` names are intentional: this API is still evolving.
49
50 ### Improvements and fixes
51
52 - `triggers.create()` now forwards `userId`, enabling trigger 2FA ownership checks.
53 - Telemetry sends no longer delay SDK results or rethrown errors.
54 - Automatic file handling now selects the correct branch for schemas that accept either one file or a list of files.
55 - Providers normalize model-produced JSON-string tool arguments and raise `ComposioInvalidToolArgumentsError` for invalid values instead of leaking raw parser errors.
56 - MCP-backed toolkits with empty or missing output schemas no longer fail validation. Mastra also tolerates unresolved backend `$ref` values without making the whole tool list unusable.