NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
PyPI · #3104 most downloaded on PyPI
SDK for integrating Composio with your applications.
Last release 5 days ago
29 Sep 2026
Ships fairly regularly
a new release about every 2 weeks
Some releases are documented
notes for 21 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
2 years old
79 releases · first in 2024
One column per month.
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
Nothing published for this version
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.Your coding agent can read these notes before it upgrades. Set up the MCP server →