---
canonical_url: "https://docs.composio.dev/docs/changelog/2026/10/22"
markdown_url: "https://docs.composio.dev/docs/changelog/2026/10/22.md"
product: "platform"
version: null
last_updated: null
---

# Changelog - Oct 22, 2026

**Documentation:** https://docs.composio.dev/docs/changelog/2026/10/22

## Python SDK 0.29.1: certificate and dependency hardening

Require a CA bundle without the compromised eMudhra root, and cap third-party dependency ranges.

This patch release hardens how the Python SDK and its providers resolve dependencies. It has no API changes.

### Release versions [#release-versions]

| SDK               | Version  |
| ----------------- | -------- |
| Python `composio` | `0.29.1` |

All 13 Python provider packages are released at `0.29.1`.

### What's changed [#whats-changed]

* **`certifi>=2026.10.19` is now required.** That bundle removes the emSign ECC Root CA - G3 root after eight eMudhra intermediate keys were compromised. Older bundles still trust certificates issued under it.
* **Third-party dependencies have upper bounds.** Each range stops before the first major version that wasn't released yet when the cap was set, or before `1.0` for packages still on `0.x`. A future major line can't install until the SDK raises the cap. Ranges can still span majors that already exist: `openai>=2.48.0,<4` allows 2.x and 3.x, and `anthropic>=0.120.0,<3` allows 0.x through 2.x. `certifi` stays uncapped so CA bundle updates always install.
* **`pysher` is pinned to `1.0.8`.** The trigger client depends on it, and it has had no release since 2022. Its transport is capped at `websocket-client<2`.
* **Releases come from a locked build.** Packages are built only from locked dependencies and published with PyPI trusted publishing, so each file on PyPI carries an attestation linking it to the GitHub workflow that built it.

Every cap sits above the newest release available today, so existing installs resolve the same versions as before.

---

## Python SDK 0.29.0: toolkit warnings and provider argument fixes

Get toolkit sunset warnings, preserve tool arguments across Python providers, and migrate direct HTTP clients.

The Python SDK now warns when the API reports that a toolkit version you use is deprecated. This release also fixes tool argument serialization and preserves more of your schemas across providers.

### Release versions [#release-versions]

| SDK               | Version  |
| ----------------- | -------- |
| Python `composio` | `0.29.0` |

All 13 Python provider packages are released at `0.29.0`.

### What's new [#whats-new]

* **Toolkit deprecation warnings.** The SDK warns once per process for each deprecated toolkit version reported through the `Composio-Deprecated-Toolkits` response header. The warning names the version, its sunset date, and how to pin a newer version. See [toolkit versioning](/docs/tools-direct/toolkit-versioning#deprecation-and-sunset).

### Migration notes [#migration-notes]

> Direct construction of `composio.client.HttpClient` now takes `auth` and `scope` instead of
credential keywords and scope headers. It no longer accepts `default_query`. The main
`Composio(api_key=...)` constructor keeps its credential options, and Python still reads
`COMPOSIO_CUSTOM_HEADERS`.

If you construct `HttpClient` directly, replace the credential keywords with an `auth` value:

Before: `HttpClient(provider="openai", api_key=key)`.

After: `HttpClient(provider="openai", auth=ProjectAuth(key))`, importing `ProjectAuth` from `composio_client`.

For organization and project routing, replace scope headers with `scope=Scope(organization_id=org_id, project_id=project_id)`, importing `Scope` from `composio_client`. Remove `default_query` from direct client construction.

### Bug fixes [#bug-fixes]

* **Pydantic aliases.** Tool execution serializes Pydantic arguments with their declared aliases, including nested models and explicit serialization aliases.
* **Provider arguments.** AutoGen and Google ADK preserve and validate free-form arguments instead of dropping them. OpenAI Agents preserves the source schema's `additionalProperties`. See the [provider behavior changes and limitations](/docs/changelog/2026/10/20).
* **Google ADK nested arrays.** The provider preserves nested array item schemas instead of replacing them with a flat string schema.

---

## SDK releases: session hooks in Python 0.30.0 and TypeScript 0.27.0

Block tool calls or results with session hooks, inspect hook outcomes, and handle blocked proxy requests.

You can now attach hooks to a session to block a tool call before it runs or block its result before your agent sees it.

### Release versions [#release-versions]

| SDK                              | Version  |
| -------------------------------- | -------- |
| Python `composio`                | `0.30.0` |
| TypeScript `@composio/core`      | `0.27.0` |
| TypeScript `@composio/slim`      | `0.27.0` |
| TypeScript `@composio/anthropic` | `0.11.6` |

All 13 Python provider packages are released at `0.30.0`.

### What's new [#whats-new]

* **Session hooks.** Pass `hooks` when you create or update a session. Hooks can run before execution or after execution, and can apply to selected toolkits. Updating `hooks` replaces the whole list; `None` in Python or `null` in TypeScript removes every hook. You cannot combine `hooks` with `experimental.session_config_id` in Python or `experimental.sessionConfigId` in TypeScript in the same call.
* **Hook outcomes.** Session execution returns `result_type="blocked"` in Python or `resultType: 'blocked'` in TypeScript when a hook blocks a call or result. The response contains empty `data`, the hook's message in `error`, and `block_reason` or `blockReason`. When hooks apply, inspect `hook_results` or `hookResults` for their outcomes. Provider integrations return blocked execution as a failed tool call with the hook's message.

### Migration notes [#migration-notes]

> Session proxy execution now distinguishes completed requests from blocked requests. A blocked
request has no HTTP response. Check the result type before reading HTTP response fields.

In Python, replace direct access to a proxy response's `status` with a result-type check:

Before: `print(response.status)`.

After: `print(response["status"] if response["result_type"] == "completed" else response["message"])`.

In TypeScript, make the equivalent check:

Before: `console.log(response.status)`.

After: `console.log(response.resultType === 'completed' ? response.status : response.message)`.

This applies to `session.proxy_execute()` and `ctx.proxy_execute()` in Python, and `session.proxyExecute()` and `ctx.proxyExecute()` in TypeScript.

### Bug fixes [#bug-fixes]

* **Python custom-tool annotations.** `@composio.experimental.tool` reports unresolved input annotations when you register the tool, with the affected parameter and the original resolution error.
* **Anthropic provider dependencies.** The TypeScript Anthropic provider removes its unused `@mastra/mcp` peer dependency, avoiding unrelated packages during installation.

---

## TypeScript SDK 0.26.0: toolkit warnings and provider schema fixes

Get toolkit sunset warnings, preserve tool schemas across TypeScript providers, and migrate direct API client access.

The TypeScript SDK now warns when the API reports that a toolkit version you use is deprecated. This release also preserves more of your tool schemas and arguments across providers.

### Release versions [#release-versions]

| SDK                                       | Version  |
| ----------------------------------------- | -------- |
| TypeScript `@composio/core`               | `0.26.0` |
| TypeScript `@composio/slim`               | `0.26.0` |
| TypeScript `@composio/json-schema-to-zod` | `0.4.0`  |
| TypeScript `@composio/claude-agent-sdk`   | `0.13.0` |
| TypeScript `@composio/vercel`             | `0.13.0` |
| TypeScript `@composio/llamaindex`         | `0.11.2` |

### What's new [#whats-new]

* **Toolkit deprecation warnings.** The SDK warns once per process for each deprecated toolkit version reported through the `Composio-Deprecated-Toolkits` response header. The warning names the version, its sunset date, and how to pin a newer version. See [toolkit versioning](/docs/tools-direct/toolkit-versioning#deprecation-and-sunset).
* **Zod v4 schema builder.** Import `jsonSchemaToZod` or `jsonSchemaToZodShape` from `@composio/json-schema-to-zod/v4` to build classic Zod v4 schemas. The root entry continues to build Zod v3 schemas. The v4 builder requires Zod `4.1.13` or newer and preserves schema annotations in metadata for `z.toJSONSchema()`.
* **Provider schema preservation.** The TypeScript Vercel and LlamaIndex providers now give the model the tool's JSON Schema directly, preserving keywords such as `format`, `contentEncoding`, and `contentMediaType`. Claude Agent SDK uses the new Zod v4 builder to preserve those annotations. Existing tool argument validation stays in place.

### Migration notes [#migration-notes]

> This release changes direct API client access, TypeScript Vercel tool schemas, and the Claude
Agent SDK provider's minimum Zod version. Apply the relevant steps below before upgrading.

1. **TypeScript client access.** Read credentials from `composio.getConfig()` instead of `composio.getClient().apiKey`, `.userApiKey`, or `.orgApiKey`. The client also removes `.logger`. Its `baseURL`, `maxRetries`, `timeout`, and `logLevel` are read-only; derive a client with `withOptions()` to change them. For example, replace `composio.getClient().maxRetries = 0` with `const client = composio.getClient().withOptions({ maxRetries: 0 })` and use the derived client for those calls.
2. **TypeScript custom headers.** Replace `COMPOSIO_CUSTOM_HEADERS` with the SDK's `defaultHeaders` option. Credential and scope headers in `defaultHeaders` or `createSession({ headers })` are folded into SDK configuration and no longer appear under `getConfig().defaultHeaders`. Supply at most one of `x-api-key`, `x-user-api-key`, or `x-org-api-key`; multiple credential headers now throw. Per-call client headers cannot override credentials or scope. With `apiKey: null` and only an organization API key, API calls, trigger authorization, and `session.mcp.headers` now consistently carry `x-org-api-key`.
3. **Vercel tool schemas.** `tool.inputSchema` is now an AI SDK `Schema`. Replace direct `tool.inputSchema.safeParse(value)` calls with `asSchema(tool.inputSchema).validate(value)`, importing `asSchema` from `ai`.
4. **Claude Agent SDK and Zod v4.** Upgrade Zod to `4.1.13` or newer before upgrading `@composio/claude-agent-sdk`. Older Zod v4 versions do not provide the shared metadata registry the builder needs.
5. **Deprecated TypeScript connection data.** For `customConnectionData` with `S2S_OAUTH2`, supply `val.access_token`, which the API requires.

### Bug fixes [#bug-fixes]

* **Strict TypeScript tool schemas.** OpenAPI `nullable` is converted into a nullable type or a null branch. Unsupported string formats, including `uri`, custom formats, and `path`, are removed before strict requests reach the model provider. This prevents a single tool schema from causing the whole request to fail.
* **String argument validation.** TypeScript checks a string as base64 only when its `contentEncoding` is `base64`. Fields with `format: "binary"` or another encoding, such as `base16`, accept plain strings instead of being rejected as invalid base64.
* **Zod v3 validation paths.** Errors inside nested object properties report each property name once, including errors from `patternProperties`, `additionalProperties`, and `oneOf`.

---