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: update documentation for new changelog entries (#5045)
## Summary Automated documentation updates triggered by new changelog entries merged to next. Generated by Codex via GitHub Actions. Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
sdkrelease[bot] committed
Oct 22, 2026 at 01:53 UTC
aed3ff874875c2d8b7decbd0bfc2445c2d3cd0ab
5 files changed
+30
docs/content/docs/providers/anthropic.mdx
+4
@@ -180,6 +180,10 @@ The `ClaudeAgentSDKProvider` exposes your Composio tools to the Claude Agent SDK
180
</Tab>
181
<Tab value="TypeScript">
182
<PackageInstall packages="@composio/core @composio/claude-agent-sdk @anthropic-ai/claude-agent-sdk" />
183
+
184
+<Callout type="warn">
185
+The TypeScript provider requires Zod `4.1.13` or newer. Upgrade Zod before upgrading `@composio/claude-agent-sdk`; older Zod v4 versions lack the shared metadata registry the provider needs to preserve schema annotations.
186
+</Callout>
187
</Tab>
188
</Tabs>
189
</Step>
docs/content/docs/providers/custom-providers/typescript.mdx
+4
@@ -164,6 +164,10 @@ export class MyAgentProvider extends BaseAgenticProvider<AgentToolkit, AgentTool
164
}
165
```
166
167
+## Build Zod schemas
168
+
169
+If your framework expects Zod v4 schemas, import `jsonSchemaToZod` or `jsonSchemaToZodShape` from `@composio/json-schema-to-zod/v4`. This entry builds classic Zod v4 schemas and requires Zod `4.1.13` or newer. It stores schema annotations in metadata so `z.toJSONSchema()` preserves them. The root `@composio/json-schema-to-zod` entry builds Zod v3 schemas.
170
+
171
## Support strict tool schemas
172
173
If your platform supports OpenAI-compatible strict tool schemas, use `toStrictJsonSchema()` to normalize each tool's input schema. The result keeps optional parameters available by making them required and nullable. Before execution, use `omitNullToolArguments()` to remove a `null` that represents an omitted optional parameter while preserving fields whose original schema accepts `null`.
docs/content/docs/providers/index.mdx
+14
@@ -11,6 +11,20 @@ Pick the provider that matches the SDK or agent framework you already use. Each
11
The TypeScript SDK is ESM-only and requires Node.js 22.22.3 or newer. Use `import` instead of CommonJS `require()`.
12
</Callout>
13
14
+## TypeScript client configuration
15
+
16
+Use `composio.getConfig()` to read SDK credentials. The client returned by `composio.getClient()` doesn't expose `apiKey`, `userApiKey`, `orgApiKey`, or `logger`. Its `baseURL`, `maxRetries`, `timeout`, and `logLevel` are read-only. To change client options for specific calls, derive a client with `const client = composio.getClient().withOptions({ maxRetries: 0 })` and use that client for those calls.
17
+
18
+Pass custom headers through the SDK's `defaultHeaders` option.
19
+
20
+<Callout type="warn">
21
+`COMPOSIO_CUSTOM_HEADERS` is no longer supported. Replace it with `defaultHeaders` when constructing the SDK.
22
+</Callout>
23
+
24
+Credential and scope headers supplied through `defaultHeaders` or `createSession({ headers })` become SDK configuration and don't appear in `getConfig().defaultHeaders`. Supply at most one credential header: `x-api-key`, `x-user-api-key`, or `x-org-api-key`. Supplying multiple credential headers throws an error. Per-call client headers cannot override credentials or scope.
25
+
26
+With `apiKey: null` and only an organization API key, API calls, trigger authorization, and `session.mcp.headers` use `x-org-api-key`.
27
+
28
## AI SDKs
29
30
Use these when you call a model SDK directly.
docs/content/docs/providers/llamaindex.mdx
+4
@@ -94,6 +94,10 @@ console.log(result.data.result);
94
</Step>
95
</Steps>
96
97
+## TypeScript tool schemas
98
+
99
+The TypeScript provider passes each tool's JSON Schema directly to the model, preserving keywords such as `format`, `contentEncoding`, and `contentMediaType`. Tool arguments are still validated before execution.
100
+
101
## Next
102
103
<Card icon={<BookOpen />} title="What is a session?" href="/docs/how-composio-works" description="How sessions scope users, tools, and auth, and how to reuse them across requests." />
docs/content/docs/providers/vercel.mdx
+4
@@ -73,6 +73,10 @@ The option does not set the AI SDK's per-tool `strict` flag, so the model provid
73
The provider sends each Composio tool's JSON Schema to the model as is, so keywords such as `format`, `contentEncoding`, and `contentMediaType` reach it, and validates tool-call arguments with a Zod schema built from the same JSON Schema. It also normalizes tool arguments, so it still works when a model emits tool input as a JSON string rather than an object.
74
</Callout>
75
76
+<Callout type="warn">
77
+`tool.inputSchema` is an AI SDK `Schema`. If you validate arguments yourself, import `asSchema` from `ai` and call `await asSchema(tool.inputSchema).validate(value)` instead of `tool.inputSchema.safeParse(value)`.
78
+</Callout>
79
+
80
## Next
81
82
<Card icon={<BookOpen />} title="What is a session?" href="/docs/how-composio-works" description="How sessions scope users, tools, and auth, and how to reuse them across requests." />