NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
PyPI, #3000 most downloaded on PyPI
SDK for integrating Composio with your applications.
Latest stable
0.32.0
Last release 13 days ago
09 Nov 2026
Ships fairly regularly
a new release about every 2 weeks
Most releases are documented
notes for 39 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
2 years old
87 releases · first in 2024
Drag across the ruler to compare, or tap a release to open it.
fa933a6: Fix the homepage links in these packages' package.json. They pointed at github.com/ComposioHQ/composio/tree/main/..., but the default branch
homepage links in these packages' package.json. They pointed at github.com/ComposioHQ/composio/tree/main/..., but the default branch is next and no main branch exists, so every link 404'd on npm and in editor tooltips. They now point at tree/next/....@composio/anthropic also accepts @anthropic-ai/sdk 0.124 as a peer, the line it is now tested against.Your coding agent can read these notes before it upgrades. Set up the MCP server →
This project publishes no release notes. Between v0.11.0 and v0.11.1 there were 242 commits, 176 of them substantive:
nodeVersion: ['current'] to echo $(.nvmrc) (#2514)…and 156 more.
9ffc696: Add AI SDK 7 support to @composio/vercel. The ai peer dependency range is now ^6.0.0 || ^7.0.0 (AI SDK 5 is no longer supported; both v6 and
@composio/vercel. The ai peer dependency range is now ^6.0.0 || ^7.0.0 (AI SDK 5 is no longer supported; both v6 and v7 are covered by e2e compatibility tests).userId when creating trigger instances so trigger 2FA flows can verify connected account ownership.composio.tools.createCustomTool(...) in-memory registry API. Use Tool Router custom tools via experimental_createTool, experimental_createToolkit, and composio.create(..., { experimental: { customTools, customToolkits } }) instead.22a9171: Defer telemetry batch and error sends so instrumentation does not wait for telemetry network requests before returning SDK results or rethrowing SDK errors.
93b67e8: Fix automatic file upload/download substitution for file schemas that accept either a single file or a list of files.
The file modifier now selects composed-schema branches by runtime value shape, so anyOf(file, array<file>) uploads or downloads each file when the tool receives a list while preserving existing single-file behavior.
b69cef1: Tolerate dangling $ref pointers in tool schemas the Composio API ships without a matching $defs entry. Some toolkits (e.g. GMAIL_FETCH_EMAILS) emit outputParameters with "$ref": "#/$defs/FetchEmailsResponse" while never declaring a top-level $defs block. After the strict resolver shipped with the previous Mastra fix, this caused composio.tools.get(...) to throw JsonSchemaRefResolutionError upfront, making every Gmail / Slack / Google-Calendar tool unusable through MastraProvider. The SDK now degrades the unresolvable branch to a permissive object schema and surfaces a single observability warning per (toolSlug, ref) pair instead of crashing.
dereferenceJsonSchema accepts a new optional second argument { onUnresolved?: 'throw' | 'sentinel'; onReplace?: (ref, reason) => void }. Default behavior is unchanged ('throw') — first-party / custom-tool schemas with a typo'd $ref still surface as a hard error. Pass 'sentinel' to replace unresolved branches with the cycle-break sentinel ({ type: 'object', additionalProperties: true }) that the resolver already uses for $ref cycles. The replaced sentinel carries a default description hint so LLMs consuming the wrapped tool's schema get an in-band signal that the branch is opaque; a caller-provided description sibling overrides the default (Draft 2020-12 sibling-keyword merge). Safety caps (MAX_REF_CHAIN_DEPTH, MAX_NODE_DEPTH) keep throwing in both modes. New UnresolvedRefStrategy, UnresolvedRefReason, and DereferenceJsonSchemaOptions type exports.MastraProvider.wrapTool opts both inputParameters and outputParameters into 'sentinel' mode and emits one logger.warn per (toolSlug, ref) pair via the provider-scoped dedup Set. User-controlled segments in the warning (tool.slug, toolkit.slug, ref) are JSON.stringifyd to neutralize embedded newlines / ANSI escapes / control bytes that could otherwise forge log lines (CWE-117). A matching one-shot telemetry event (composio.mastra.wrapTool.danglingRef) fires next to the warn so the Composio team has aggregate visibility into which toolkits are affected; the event respects COMPOSIO_DISABLE_TELEMETRY=true.telemetry instance from @composio/core is now publicly re-exported alongside logger, so providers can emit aggregate signals without reaching into the package's internals.$defs / definitions continue to be inlined exactly as before — no regression in the type-info preservation contract introduced by the previous Mastra fix.1ba66ca: Fix tools.execute (and tools.get / tools.list) failing with a ZodError for every tool from an MCP-backed toolkit (e.g. granola_mcp, apify_mcp, tavily_mcp).
MCP toolkits don't declare an output schema, and the Composio API serializes that as output_parameters: {}. The SDK's ParametersSchema required { type: 'object', properties: {...} }, so transformToolCases rejected the response and getRawComposioToolBySlug — called by execute and the list path — threw.
The SDK now normalizes empty ({}), null, and missing input_parameters / output_parameters payloads to undefined before validation. outputParameters was already declared .optional() in the public Tool type, so this preserves the contract: "undefined means no declared schema." Tools that do declare a schema continue to be validated strictly.
No public API change; no toolkit allow-list.
ce4b213: fix(providers): normalize string tool-call arguments across all providers
Models occasionally emit tool-call arguments as a JSON string instead of an
object (most visibly with COMPOSIO_MULTI_EXECUTE_TOOL on the Vercel AI SDK),
which broke downstream validation with errors like
tool_use.input: Input should be a valid dictionary.
@composio/core now exposes a single normalizeToolArguments helper, and every
provider routes model-supplied arguments through it. Object payloads pass
through unchanged, JSON strings are parsed, empty/null payloads become {},
and anything that cannot resolve to an object throws a typed
ComposioInvalidToolArgumentsError instead of a raw SyntaxError or a silently
forwarded malformed string. This replaces the inconsistent per-provider guards
that previously existed only in vercel, cloudflare and openai-agents.
executeToolCall and the OpenAI Responses provider's handleResponse to execute through a supplied Tool Router session, matching the other provider helpers. Session meta-tools now keep their session context through these helpers. Existing user-ID calls keep using direct execution unchanged, and the Cloudflare options argument is now optional. Passing a session requires @composio/core 0.17.0 or later. Custom provider subclasses overriding these methods may require updates because they now accept session targets.9447932: Dereference internal $ref/$defs in tool input schemas before provider translation, so properties reachable only through a reference keep their types and validation instead of degrading to untyped (z.any) or being emitted as a dangling reference.
This changes the JSON Schema these providers emit for $ref-using tools. Downstream snapshot tests on tool definitions will see diffs. Schemas the Composio API ships with a $ref but no $defs block (e.g. GMAIL_FETCH_EMAILS) degrade to a permissive object schema rather than throwing. The strict-structured-outputs path of @composio/openai-agents is unchanged — OpenAI supports $defs/$ref natively, including recursion.
{ error } results without changing successful payloads. Custom provider subclasses overriding executeToolCall or handleToolCalls may require updates because these methods now accept session targets.ac6bbab: Register each tool with its complete schema, so root rules reach the Claude Agent SDK.
The provider used to register a raw property shape. A raw shape is only the map of named properties, so it cannot carry any root rule. additionalProperties and patternProperties were dropped before the SDK saw them.
Two things went wrong because of that. Free-form object arguments lost their content. An argument the tool never declared was quietly removed, and the tool ran anyway.
Both are fixed. The provider now registers the whole object schema.
What no longer works
An undeclared argument no longer passes silently.
// The tool declares `to` and nothing else. The model also sends `hallucinated`.
{ to: 'someone@example.com', hallucinated: 'value' }
// before: `hallucinated` was stripped, and the tool ran with { to: '...' }
// now: the caller receives an error result, and the tool does not run
Tools with no input parameters behave the same way. They stay closed and reject every argument.
What to do instead
If the model should be allowed to send extra keys, say so in the tool schema:
{
"type": "object",
"properties": { "to": { "type": "string" } },
"additionalProperties": true
}
If an argument is one the tool really accepts, declare it in properties. Rejection is usually the better outcome, because the agent sees the error and can correct itself instead of running with a silently dropped argument.
This brings the provider in line with @composio/vercel, @composio/langchain, and @composio/llamaindex, which already registered complete schemas.
This project publishes no release notes. Between v0.10.6 and v0.11.0 there were 250 commits, 208 of them substantive:
…and 188 more.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
fd59eba: Update SDK and provider dependencies to compatible releases. Accept Anthropic SDK 0.132 and OpenAI Agents 0.20 in provider peer ranges, and a
This project publishes no release notes. Between v0.10.5 and v0.10.6 there were 22 commits, 19 of them substantive:
tsdown + introduce e2e tests (#2360)composio.triggers.verifyWebhooks (#2361)62e51e8: Refresh runtime dependencies and extend provider peer compatibility to the latest supported Anthropic and OpenAI Agents SDK releases.
@composio/anthropic also accepts @anthropic-ai/sdk 0.124 as a peer, the line it is now tested against.This project publishes no release notes. Between v0.10.4 and v0.10.5 there were 4 commits, 4 of them substantive:
auto_upload_download_files boolean flag to Composio() (#2334)db7b576: Declare Node.js 22.22.3 as the minimum supported runtime for every published TypeScript package so package managers surface incompatible runt
MastraProvider({ strict: true }) now keeps optional parameters instead of dropping them: every property becomes required and optional ones accept null, matching the OpenAI providers, and a null argument the tool's own schema does not accept is dropped before execution. Tools whose schema strict mode cannot express keep their original schema with a warning.This project publishes no release notes. Between v0.10.2 and v0.10.4 there were 125 commits, 115 of them substantive:
…and 95 more.
db7b576: Declare Node.js 22.22.3 as the minimum supported runtime for every published TypeScript package so package managers surface incompatible runt
@composio/anthropic also accepts @anthropic-ai/sdk 0.124 as a peer, the line it is now tested against.58bc93b: Refresh dependency ranges and lockfiles across the workspace.
homepage links in these packages' package.json. They pointed at github.com/ComposioHQ/composio/tree/main/..., but the default branch is next and no main branch exists, so every link 404'd on npm and in editor tooltips. They now point at tree/next/....OpenAIAgentsProvider({ strict: true }) now takes effect: tools are registered with strict: true and a schema normalized for OpenAI structured outputs (every property required, optional ones accept null), a null argument the tool's own schema does not accept is dropped before execution, and tools whose schema strict mode cannot express are registered without strict mode with a warning. The option was previously ignored.@composio/core >=0.16.0 <1.0.0 for the shared schema normalizer.This project publishes no release notes. Between v0.10.1 and v0.10.2 there were 133 commits, 114 of them substantive:
…and 94 more.
7125576: Normalize duplicate JSON Schema required entries before provider tool schemas are emitted.
required entries before provider tool schemas are emitted.homepage links in these packages' package.json. They pointed at github.com/ComposioHQ/composio/tree/main/..., but the default branch is next and no main branch exists, so every link 404'd on npm and in editor tooltips. They now point at tree/next/....required entries before provider tool schemas are emitted.homepage links in these packages' package.json. They pointed at github.com/ComposioHQ/composio/tree/main/..., but the default branch is next and no main branch exists, so every link 404'd on npm and in editor tooltips. They now point at tree/next/....@mastra/core peer dependency range.This project publishes no release notes. Between v0.10.0 and v0.10.1 there were 3 commits, 3 of them substantive:
composio generate --toolkits [toolkits] support, for both ts and py (#2252)025a657: Drop CommonJS entrypoints and publish the TypeScript SDK packages as ESM-only packages. This is a breaking change within the existing 0.x rel…
require(esm) interop, and the SDK no longer ships custom CommonJS compatibility machinery or .cjs artifacts.require(esm) interop, and the SDK no longer ships custom CommonJS compatibility machinery or .cjs artifacts.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.require(esm) interop, and the SDK no longer ships custom CommonJS compatibility machinery or .cjs artifacts.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.require(esm) interop, and the SDK no longer ships custom CommonJS compatibility machinery or .cjs artifacts.507318d: Harden the Anthropic tool property-key sanitizer:
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.@composio/core (sanitizeSchemaPropertyKeys / restoreOriginalKeys); this provider supplies only the Anthropic key constraint as a policy, reusing core's prototype-pollution guard and depth cap.Object.prototype member (__proto__, constructor, toString, hasOwnProperty, …) no longer throws or silently corrupts the payload sent to the backend. Object.prototype is never mutated.{1,64} length bound.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.
42ebff3: feat(connected-accounts): namespace SHARED-connection surface under experimental
Aligns the TypeScript SDK with the experimental wire shape used by Shared Connections. The flat accountType / aclConfigForShared options on connectedAccounts.link() and session.authorize() have moved under a single experimental block, and connectedAccounts.updateAcl() has moved off the class onto a top-level experimental_updateAcl(composio, id, opts) export — same precedent as experimental_createTool / experimental_createToolkit.
The experimental namespace is the signal that the shape may change in future releases. Pinning a SHARED connection in a session config (connectedAccounts: { gmail: [...] }) and direct execute by connectedAccountId are unchanged — only the connection-create / patch / authorize surfaces are namespaced.
Also surfaces the accountType filter on connectedAccounts.list() so SHARED connections can be listed without dropping to the raw client. The wire keeps this as a flat query param, so the SDK keeps it flat too.
@composio/client bumped from 0.1.0-alpha.71 → 0.1.0-alpha.72 so the generated typed client carries the Experimental namespaces for link.create, toolRouter.session.link, and connectedAccounts.patch.
Caller migration:
// before
await composio.connectedAccounts.link('user_id', 'auth_config_id', {
accountType: 'SHARED',
aclConfigForShared: { allowAllUsers: true },
});
await composio.connectedAccounts.updateAcl('ca_abc', { allowAllUsers: true });
await session.authorize('github', {
accountType: 'SHARED',
aclConfigForShared: { allowAllUsers: true },
});
// after
await composio.connectedAccounts.link('user_id', 'auth_config_id', {
experimental: {
accountType: 'SHARED',
aclConfigForShared: { allowAllUsers: true },
},
});
await experimental_updateAcl(composio, 'ca_abc', { allowAllUsers: true });
await session.authorize('github', {
experimental: {
accountType: 'SHARED',
aclConfigForShared: { allowAllUsers: true },
},
});
// new — list SHARED connections
const shared = await composio.connectedAccounts.list({
accountType: 'SHARED',
userIds: ['user_creator'],
});
This project publishes no release notes. Between v0.9.5-rc.1 and v0.10.0 there were 76 commits, 65 of them substantive:
…and 45 more.
Nothing published for this version
Nothing published for this version
This project publishes no release notes. Between v0.9.4 and v0.9.5-rc.1 there were 6 commits, 6 of them substantive:
This project publishes no release notes. Between v0.9.4 and v0.9.5-rc.1 there were 6 commits, 6 of them substantive:
Nothing published for this version
ce4b213: fix(providers): normalize string tool-call arguments across all providers
ce4b213: fix(providers): normalize string tool-call arguments across all providers
Models occasionally emit tool-call arguments as a JSON string instead of an
object (most visibly with COMPOSIO_MULTI_EXECUTE_TOOL on the Vercel AI SDK),
which broke downstream validation with errors like
tool_use.input: Input should be a valid dictionary.
@composio/core now exposes a single normalizeToolArguments helper, and every
provider routes model-supplied arguments through it. Object payloads pass
through unchanged, JSON strings are parsed, empty/null payloads become {},
and anything that cannot resolve to an object throws a typed
ComposioInvalidToolArgumentsError instead of a raw SyntaxError or a silently
forwarded malformed string. This replaces the inconsistent per-provider guards
that previously existed only in vercel, cloudflare and openai-agents.
b69cef1: Tolerate dangling $ref pointers in tool schemas the Composio API ships without a matching $defs entry. Some toolkits (e.g. GMAIL_FETCH_EMAILS) emit outputParameters with "$ref": "#/$defs/FetchEmailsResponse" while never declaring a top-level $defs block. After the strict resolver shipped with the previous Mastra fix, this caused composio.tools.get(...) to throw JsonSchemaRefResolutionError upfront, making every Gmail / Slack / Google-Calendar tool unusable through MastraProvider. The SDK now degrades the unresolvable branch to a permissive object schema and surfaces a single observability warning per (toolSlug, ref) pair instead of crashing.
dereferenceJsonSchema accepts a new optional second argument { onUnresolved?: 'throw' | 'sentinel'; onReplace?: (ref, reason) => void }. Default behavior is unchanged ('throw') — first-party / custom-tool schemas with a typo'd $ref still surface as a hard error. Pass 'sentinel' to replace unresolved branches with the cycle-break sentinel ({ type: 'object', additionalProperties: true }) that the resolver already uses for $ref cycles. The replaced sentinel carries a default description hint so LLMs consuming the wrapped tool's schema get an in-band signal that the branch is opaque; a caller-provided description sibling overrides the default (Draft 2020-12 sibling-keyword merge). Safety caps (MAX_REF_CHAIN_DEPTH, MAX_NODE_DEPTH) keep throwing in both modes. New UnresolvedRefStrategy, UnresolvedRefReason, and DereferenceJsonSchemaOptions type exports.MastraProvider.wrapTool opts both inputParameters and outputParameters into 'sentinel' mode and emits one logger.warn per (toolSlug, ref) pair via the provider-scoped dedup Set. User-controlled segments in the warning (tool.slug, toolkit.slug, ref) are JSON.stringifyd to neutralize embedded newlines / ANSI escapes / control bytes that could otherwise forge log lines (CWE-117). A matching one-shot telemetry event (composio.mastra.wrapTool.danglingRef) fires next to the warn so the Composio team has aggregate visibility into which toolkits are affected; the event respects COMPOSIO_DISABLE_TELEMETRY=true.telemetry instance from @composio/core is now publicly re-exported alongside logger, so providers can emit aggregate signals without reaching into the package's internals.$defs / definitions continue to be inlined exactly as before — no regression in the type-info preservation contract introduced by the previous Mastra fix.ce4b213: fix(providers): normalize string tool-call arguments across all providers
Models occasionally emit tool-call arguments as a JSON string instead of an
object (most visibly with COMPOSIO_MULTI_EXECUTE_TOOL on the Vercel AI SDK),
which broke downstream validation with errors like
tool_use.input: Input should be a valid dictionary.
@composio/core now exposes a single normalizeToolArguments helper, and every
provider routes model-supplied arguments through it. Object payloads pass
through unchanged, JSON strings are parsed, empty/null payloads become {},
and anything that cannot resolve to an object throws a typed
ComposioInvalidToolArgumentsError instead of a raw SyntaxError or a silently
forwarded malformed string. This replaces the inconsistent per-provider guards
that previously existed only in vercel, cloudflare and openai-agents.
### Patch Changes - Updated dependencies [42ebff3] - @composio/core@0.10.0
### Patch Changes - Updated dependencies [84a3a07] - Updated dependencies [c358ffa] - @composio/core@0.9.1
84a3a07: Add accountType and per-user ACL support for SHARED connected accounts.
accountType on create: composio.connectedAccounts.link(userId, authConfigId, { accountType: 'SHARED' }) creates a SHARED connection. Default remains PRIVATE. A SHARED connection can be used by other userIds, but only when the connection is explicitly pinned in a tool-router session's config and only when the requesting userId passes the connection's ACL.accountType on retrieve: get() and list() responses now include accountType ('PRIVATE' | 'SHARED').aclConfigForShared on create + retrieve: per-user ACL block — { allowAllUsers, allowedUserIds, notAllowedUserIds }. On responses the field is undefined when the caller isn't authorised to see the ACL, so callers can distinguish "I can't see the ACL" from "ACL is the default deny-by-default state".updateAcl() method (new): composio.connectedAccounts.updateAcl(nanoid, { allowAllUsers, allowedUserIds, notAllowedUserIds }) writes the ACL via PATCH. PATCH semantics — omit a field to leave it unchanged; pass an empty array to clear an allow/deny list. At least one field required. Calling on a PRIVATE connection raises ComposioAclOnlyForSharedError (400).ToolRouterSession.authorize() options gain accountType + aclConfigForShared, so a SHARED connection with an ACL can be created in one call from inside a tool-router session.ACL resolution rule (deny wins):
userId ∈ notAllowedUserIds → DENYallowAllUsers === true → ALLOWuserId ∈ allowedUserIds → ALLOWLimits: each ACL list accepts up to 1000 entries; each userId is 1..256 characters. The SDK enforces these caps at the input boundary.
New error classes:
ComposioSharedAccessDeniedError (403) — surfaces from direct connectedAccountId execution paths when the requesting user fails the ACL.ComposioAclOnlyForSharedError (400) — ACL fields sent on a PRIVATE connection.ComposioSharedConnectionNotAccessibleError (400) — tool-router session create / PATCH with a pinned SHARED connection the session user cannot use.No breaking changes. Existing link() callers without the new options get a PRIVATE connection exactly as today; existing get() / list() callers see new optional fields.
The Python SDK mirror ships in a separate PR.
c358ffa: Fix false-positive initiate() deprecation warning for custom auth configs (SEC-339 follow-up).
composio.connectedAccounts.initiate() previously emitted a one-time console.warn on every redirectable-OAuth response, regardless of whether the auth config was Composio-managed (subject to the 2026-07-03 cutover) or custom (unaffected). The wording was conditional ("If this auth config is Composio-managed…") so callers using their own OAuth apps could ignore it, but the warning still printed and caused noise in logs.
Apollo already emits the SEC-339 Deprecation / Sunset / Link rel="deprecation" headers (RFC 9745 / RFC 8594) only on the retiring branch — managed + redirectable OAuth. The SDK now reads the Deprecation header from the response (via APIPromise.withResponse()) and gates the warning on its presence. Custom auth configs and non-OAuth schemes get a clean response from the server and now stay silent in the SDK as well.
initiate() calls against custom OAuth auth configs or non-OAuth schemes (API key, bearer, basic). Managed-OAuth callers continue to get exactly one warning per process, now with revised wording that points at the response's Sunset header for the precise cutover date.initiate() returns the same ConnectionRequest shape and respects the same allowMultiple guard. ComposioLegacyConnectedAccountsEndpointRetiredError continues to surface from the 400 retired-path response.mockApiPromiseWithHeaders() in connectedAccounts.test.ts wraps a value as an APIPromise-shaped thenable so the new tests can simulate apollo's header behavior. Pre-existing initiate tests using mockResolvedValueOnce continue to pass via the SDK's defensive fallback when withResponse is absent on the mock.Python SDK gets the matching change in the same release train.
Bumped to align with @composio/core@0.9.0 for the Tool Router release train. No public-API change in this provider package.
@composio/core@0.9.0 for the Tool Router release train. No public-API change in this provider package.@composio/core@0.9.0 for the Tool Router release train. No public-API change in this provider package.cc673b6: Resolve internal JSON Schema $ref pointers (#/$defs/... and #/definitions/...) before handing tool parameters to @mastra/schema-compat. Composio tools whose schemas use $defs/definitions — legal under Draft 7 and 2020-12 — no longer trigger the AJV can't resolve reference … error, and the resolved type information from $defs survives the JSON-Schema → Zod → JSON-Schema round-trip instead of being silently degraded to a permissive anyOf.
dereferenceJsonSchema helper exported from @composio/core performs the inline expansion. It deep-clones the input, walks every applicator reflectively (so future JSON Schema keywords are covered), shallow-merges sibling keywords next to $ref per Draft 2020-12 semantics, breaks cycles with { type: 'object', additionalProperties: true } (matching the upstream guidance in mastra-ai/mastra#15341), and strips $defs/definitions once everything reachable is inlined. External (http:///https://) $ref pointers are left untouched.@composio/mastra calls the helper inside wrapTool for both inputParameters and outputParameters.@mastra/schema-compat dependency floor raised to ^1.2.9 so users automatically receive PR #15400's recursive-$ref handling.Updated dependencies [c9b6525]
Updated dependencies [cc673b6]
Updated dependencies [9f14971]
Updated dependencies [81f8027]
Updated dependencies [711a703]
Updated dependencies [bccd32b]
Updated dependencies [bccd32b]
Updated dependencies [07c9bab]
Updated dependencies [3ece424]
9f14971: Add migration tooling for the link auth migration: callers using composio.connectedAccounts.initiate() for Composio-managed auth configs on redirectable OAuth schemes (OAuth1, OAuth2, DCR_OAUTH) now get a typed error and a one-time deprecation warning ahead of the 2026-07-03 all-orgs cutover.
ComposioLegacyConnectedAccountsEndpointRetiredError, exported from @composio/core. Thrown by initiate() when the underlying POST /api/v3/connected_accounts returns a 400 indicating the retiring path. Carries the migration message and a possibleFixes block pointing at link() and the migration guide.console.warn from initiate() when the response indicates a redirectable OAuth scheme. Wording is conditional ("If this auth config is Composio-managed…") so callers using custom OAuth apps or non-OAuth schemes can ignore it without ambiguity.initiate() now flags the retirement explicitly and points at link() for the affected combination. Custom auth configs and non-OAuth schemes (API key, bearer, basic) are unaffected.No behavior change for any caller outside the Composio-managed-OAuth combination — initiate() continues to call the legacy endpoint, return the same ConnectionRequest shape, and respect the allowMultiple guard.
81f8027: Add session.update() method for partially updating session configuration after creation. Accepts the same config shape as create() and mutates the session in-place. Available in both TypeScript and Python SDKs.
711a703: Add expanded ToolRouter session controls for agent workflows. composio.create()
now creates a fresh session on each call for better isolation and observability,
while composio.use() can resume an existing session for multi-turn
conversations. Sessions can preload frequently used tools, expose custom tools
directly from session.tools(), use a direct-tools preset for agents that know
their tool set upfront, and update session config mid-session with
session.update().
07c9bab: connectedAccounts now accepts both string and string[] per toolkit.
A single string is automatically coerced to an array to match the v3.1 API wire format. Existing callers passing { gmail: "ca_xxx" } continue to work without changes. Only one account per toolkit is allowed when multi-account mode is disabled.
3ece424: Add custom tools support to composio.use().
composio.use(id, { customTools, customToolkits }): Reuse an existing session and optionally bind SDK-local custom tools for search and execution.use() now correctly passes inlineCustomToolsPayload and preloadedCustomToolSlugs to the session, enabling custom tool execution and preloading on rehydrated sessions.CustomToolsMap.tools: The map now caches the raw CustomTool[] array for future inline re-injection on v3.1 search/execute requests.c9b6525: Fix connectedAccounts TypeScript type so a single string per toolkit is actually accepted by the public API.
Previously the schema's .transform() made ToolRouterCreateSessionConfig['connectedAccounts'] resolve to Record<string, string[]> (the post-transform output), so TypeScript users still got Type 'string' is not assignable to type 'string[]' even though the runtime accepted strings. Coercion now happens inside ToolRouter.create, mirroring the Python implementation, and the public type is Record<string, string | string[]>.
cc673b6: Resolve internal JSON Schema $ref pointers (#/$defs/... and #/definitions/...) before handing tool parameters to @mastra/schema-compat. Composio tools whose schemas use $defs/definitions — legal under Draft 7 and 2020-12 — no longer trigger the AJV can't resolve reference … error, and the resolved type information from $defs survives the JSON-Schema → Zod → JSON-Schema round-trip instead of being silently degraded to a permissive anyOf.
dereferenceJsonSchema helper exported from @composio/core performs the inline expansion. It deep-clones the input, walks every applicator reflectively (so future JSON Schema keywords are covered), shallow-merges sibling keywords next to $ref per Draft 2020-12 semantics, breaks cycles with { type: 'object', additionalProperties: true } (matching the upstream guidance in mastra-ai/mastra#15341), and strips $defs/definitions once everything reachable is inlined. External (http:///https://) $ref pointers are left untouched.@composio/mastra calls the helper inside wrapTool for both inputParameters and outputParameters.@mastra/schema-compat dependency floor raised to ^1.2.9 so users automatically receive PR #15400's recursive-$ref handling.bccd32b: Expose and document the Tool Router direct-tools preset via SessionPreset.DIRECT_TOOLS, with Python parity through SESSION_PRESET_DIRECT_TOOLS. Direct-tools examples now use the constants and keep the agent prompt generic while still asserting that only direct tools are exposed.
bccd32b: Document and tighten Tool Router preload behavior for app tools, preload.tools = "all", and SDK custom tools. Custom tool and toolkit preload hints now have clearer user-facing comments, direct custom tool descriptions now only state that search is not needed beforehand, examples assert the normalized LOCAL_* tool slugs exposed by session.tools(), and composio.use(..., customTools/customToolkits) reuses the same custom preload preparation path as session creation.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
6b986cd: Bring connectedAccounts.link() to parity with connectedAccounts.initiate() by adding the allowMultiple option and the matching active-connect
6b986cd: Bring connectedAccounts.link() to parity with connectedAccounts.initiate() by adding the allowMultiple option and the matching active-connection guard. With customers being migrated off connected_accounts/create (initiate) onto connected_accounts/link (SEC-339), the guard moves with them.
link(userId, authConfigId, { allowMultiple }). When allowMultiple is false (default) and the user already has an ACTIVE connection on the auth config, link() throws ComposioMultipleConnectedAccountsError — same behavior as initiate(). Pair with alias and a session-level multiAccount config to disambiguate at execution time.link() now performs a connectedAccounts.list({ userIds, authConfigIds, statuses: ['ACTIVE'] }) pre-flight before calling client.link.create. Callers that intentionally create multiple connections per auth config must pass allowMultiple: true.Python parity: same option (allow_multiple: bool = False) and same guard added to composio.connected_accounts.link().
1c3276b: Add workbench.sandboxSize to the Tool Router session config so callers can pick the workbench sandbox compute tier.
workbench.sandboxSize?: 'standard' | 'medium' | 'large' | 'xlarge' on ToolRouterCreateSessionConfig. Forwarded to the API as snake_case workbench.sandbox_size. Optional; the server defaults it to 'standard' (1 vCPU / 1 GB) when omitted, so existing callers keep current behavior.SandboxSize literal union and SandboxSizeSchema zod enum, exported from @composio/core so callers can pass tier values without stringly-typing them.@composio/client peer to 0.1.0-alpha.67 to pick up the matching sandbox_size field on the Tool Router session params.Tiers: standard (1 vCPU / 1 GB), medium (2 / 2), large (4 / 4), xlarge (8 / 8). Sandboxes are not billed today; usage-based pricing is planned. See the changelog entry at docs/content/changelog/04-28-26-sdk-sandbox-size.mdx for usage and the full tier table.
Provider packages that depend on @composio/core receive automatic patch bumps in the same release train via the changesets updateInternalDependencies: "patch" setting — no public-API change in those packages.
Nothing published for this version
dafe138: Reject root schema composition that can hide required arguments, require explicitly supplied values for prototype-named arguments, and preser
__proto__ as caller data during execution.exclusiveMinimum/exclusiveMaximum flags (as emitted by OpenAPI 3.0 exporters) into their Draft 7 numeric spelling so exclusive bounds are enforced instead of silently ignored.025a657: Drop CommonJS entrypoints and publish the TypeScript SDK packages as ESM-only packages. This is a breaking change within the existing 0.x rel…
require(esm) interop, and the SDK no longer ships custom CommonJS compatibility machinery or .cjs artifacts.One column per month.