Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
@composio/core
0.31.0
Minor Changes
- 7a1e7db: Choose which Composio-managed app an auth config uses.
composio.toolkits.get(slug)returnscomposioManagedAuthin TypeScript, one entry per managed app withmanagedAppIdandisDefault. Pass that id asmanagedAppId(TypeScript) ormanaged_app_id(Python) tocomposio.authConfigs.create/composio.auth_configs.create; omit it for the toolkit's default app. Auth config create, get and list responses returnmanagedAppIdin TypeScript (nullwhen the auth config isn't on a managed app).
Patch Changes
- dbcecde: Update the API client dependencies to 2.1.36 to include the latest API changes.
0.30.0
Minor Changes
- 6f8a704: Custom toolkits are no longer experimental. Use
composio.customToolkitsin TypeScript andcomposio.custom_toolkitsin Python.composio.experimental.customToolkitsandcomposio.experimental.custom_toolkitsare deprecated aliases of the same object and keep working. Python also exports the class asCustomToolkits;ExperimentalCustomToolkitsstays as an alias. - 84fb5ba: Surface the server's error details on every API failure, not only the default
tools.executepath.
TypeScript: apiErrorCode is now on ComposioError, derived from the APIError cause like statusCode and requestId, so every SDK wrapper gets it. The 429 branch, the 1803 connected-account branch, tool-fetch failures, and session/Tool Router execution now use the server's message, suggested_fix, status, and numeric code. Failures that never reached the API keep their original reason in the message. ComposioConnectedAccountNotFoundError keeps its 404 default but uses the server's status when it wraps an API error. Server-controlled error text is stripped of control characters and ANSI/OSC escapes before it reaches a message or terminal output.
Python: status errors raised by the SDK now expose api_error_code, suggested_fix, and possible_fixes, and api_error_details(error) gives type checkers a typed view of them. possible_fixes uses the server's suggested_fix when present and otherwise returns guidance for the HTTP status, so 401, 402, 403, 410, and 5xx no longer suggest checking the tool slug and arguments. Server-controlled text is sanitized before it reaches a message. The message already carries the server's explanation; a regression test now locks that. A tool-fetch 400/404 mapped to ToolNotFoundError now appends the server's message.
- be92189: Surface the API's error details when
tools.executefails.ComposioErrornow declaresstatusCodeandrequestId, read from the@composio/clientAPIErrorit wraps unless passed explicitly, andComposioToolExecutionErroraddsapiErrorCode, the numericerror.codethe API sent.codestays the SDK'sTS-SDK::code. Branch onerror.statusCode(for example410) instead of matching message text.
Behavior change: a rejected execution's message now ends with the server's message, and its possibleFixes come from the server's suggested_fix.
// before
error.message; // 'Error executing the tool GITHUB_GET_REPOS'
error.possibleFixes; // ['Ensure the tool slug is correct and the input arguments for the tool is valid']
// now
error.message; // 'Error executing the tool GITHUB_GET_REPOS: <the API error message>'
error.possibleFixes; // ['<the API suggested_fix>']
Without a suggested_fix, the fix depends on the HTTP status: a 401, 402, 403, 410 or 5xx no longer suggests checking the tool slug and arguments. A response that is not the API error envelope keeps the old message. ComposioConnectedAccountNotFoundError (API code 1803) now keeps the client error as cause, and errors that wrap an APIError cause, such as ComposioToolFetchError, now carry its statusCode and requestId. ComposioAPIServerErrorBody is now the client's APIErrorBody, where request_id and suggested_fix are optional, as the API sends them.
Patch Changes
- 41c4666: Allow
RemoteFile.save()to save to an explicit path when the home directory cannot be resolved. - 19a7a09: Update the API client dependencies to 2.1.33 to include the latest API changes.
- 24dfd33: Let
composio.files.upload()andcomposio.files.download()be cancelled. Both now accept trailing request options ({ signal }), like the other SDK methods that do HTTP I/O. The signal reaches the presigned-URL request and the S3 transfer, and an aborted call rejects withComposioRequestCancelledErrorinstead of running to completion. Calls cancelled byAbortSignal.timeout()or byabort(reason)during a direct S3 transfer now also reject withComposioRequestCancelledErrorrather than the signal's raw reason. - 23360bb: Stop connection polling at the deadline after a rate-limited response. When a
429withRetry-Afterreaches the timeout,waitForConnection()andwait_for_connection()now time out instead of sending another status request with a fresh client retry cycle. - 4ee12da: Use generated client types for inline local-tool payloads and share Python result handling between session tool and meta-tool execution. Public methods and request and response shapes are unchanged.
- d5c1861: Update runtime dependencies, require patched Zod 4 releases where used directly, support Anthropic SDK 1.6, and update the AutoGen provider's FLAML dependency. Preserve Zod 3 compatibility fixtures and existing framework version boundaries.
- 6aa3f31: Tolerate malformed tool schemas instead of failing a whole toolkit's tool list.
getRawComposioToolsand the raw list path previously ran every tool's parameters through the strict schema validator withparse, so one tool whose schema used a valid-but-unusual JSON Schema shape — a boolean schema node (items: true, still emitted by MCP toolkits), a draft-04 booleanexclusiveMinimum/exclusiveMaximum, or a bare combinator root with notype: "object"— threw aZodErrorand returned no tools at all for that toolkit (8 of 1562 toolkits ship such tools). Those shapes are now rewritten into the strict subset, preserving their meaning (truebecomes{},falsebecomes{ not: {} }— coercing it to{}would invert the schema). If a schema still cannot be repaired, the tool is skipped with a warning when its input schema failed — providers build their call schema from it, so a tool without one is not callable — and returned without the output schema when only that side failed. Identity-field failures stay loud. - b2b9d38: Match the
toolkitsfilter oftriggers.subscribe()for toolkits whose slug contains an underscore
The toolkit of an incoming event is derived from the first _ segment of its trigger slug, so ONE_DRIVE_FILE_CREATED_TRIGGER was attributed to ONE and subscribe(fn, { toolkits: ['one_drive'] }) dropped every OneDrive event. The same happened to launch_darkly and agent_mail. A toolkits entry now also matches when the trigger slug starts with <toolkit>_.
- Updated dependencies [d5c1861]
- @composio/json-schema-to-zod@0.4.1
0.29.0
Minor Changes
- f22ab26: Breaking (experimental API):
composio.experimental.customToolkits.create()andupsert()take the MCP server URL asmcpUrlinstead ofappUrl, and send it to the API asmcp_url. - f22ab26: Renames in-process custom tools to local tools, so they are no longer confused with the server-side custom toolkits on
composio.experimental.customToolkits. Passexperimental.localToolsandexperimental.localToolkitstocomposio.create(), andlocalToolsandlocalToolkitstocomposio.use(). List them withsession.localTools()andsession.localToolkits(). The types are nowLocalTool,LocalToolkit,RegisteredLocalTool,RegisteredLocalToolkit,CreateLocalToolParams,CreateLocalToolkitParamsandLocalToolExecuteFn. ThecustomToolsandcustomToolkitsoptions, thesession.customTools()andsession.customToolkits()methods, and theCustom*type names are deprecated and keep working. Passing both a new option and its deprecated alias throwsValidationError. The request sent to the API is unchanged. - f22ab26: Handle rate limits better:
tools.execute()reuses tool schemas instead of fetching one per call,waitForConnection()backs off between polls and waits out a 429, and tool fetches and executions rejected with a 429 throwComposioToolFetchRateLimitErrororComposioToolExecutionRateLimitError(check withisComposioRateLimitError).
Patch Changes
- f22ab26: Update @composio/client to 2.1.0 to include the latest API changes.
0.28.0
Minor Changes
- d2d4148: Requires
@composio/client2.0.0. POST and PATCH requests, including tool execution and trigger creation, are now sent once instead of being retried on a lost response or a retryable status, because a write can complete on the server after its response is lost. Other requests keep their retries. On the client returned bygetClient(), a write retries only when that call setsmaxRetries. - e87ed85: Requires
@composio/client2.0.0-rc.20. The SDK imports the client's types from the one@composio/client/resources/*spelling rc.20 publishes and reaches nested types by indexed access; every type the SDK exports keeps its shape. With rc.20, the resources of the client returned bygetClient()are plain objects typed by interfaces: the resource classes,Composio.Tools-style statics and namespace-member types such asSessionCreateParams.Experimentalare gone, and the.js/.mjssubpath spellings no longer resolve. - 3f3df9a: Requires
@composio/client2.0.0-rc.21. The SDK's behaviour is unchanged. With rc.21, the client returned bygetClient()no longer hasrequest(),Composio.ComposioorComposio.DEFAULT_TIMEOUT: call the raw verb for the method (get,post,patch,put,delete), which takes the samequery,bodyand request options. - 54a935f: Requires
@composio/client2.0.0-rc.23.composio.sessionConfigs.list()no longer sendssearch, which the Composio API removed: the option is deprecated, ignored, and logs a warning when set; filteritemsby name instead. With rc.23, the client returned bygetClient()no longer hascli.createCodactFailure(now underclient._internal, typed through@composio/client/internal) ororg.clanker.createClaim, and itssessionConfigs.list()no longer acceptssearch. - 7434e02: Requires
@composio/client2.0.0-rc.22.composio.toolkits.get(slug)now returnsmeta.appUrlwhen the API sends the toolkit's app URL; it was always left out before.composio.sessionConfigs.get()keeps therequire_approvallists of a stored policy, and no longer fails validation on a policy entry that only setsrequire_approval;SessionConfigPolicygains the matching optionalrequire_approvalfields and the approval-only entry. Session hooks, blocked calls and hook results are read from the API types of@composio/clientinstead of SDK copies, with the same results and errors for well-formed responses; a malformedhook_resultsor blocked response is no longer re-validated by the SDK, matching every other API response. - a5a1fc8: Requires
@composio/client2.0.1. Addscomposio.experimental.customToolkits.create()andupdate(), which call the v3.1 custom toolkit create and update endpoints.create()takesuserId('all'to share the toolkit, or the user it is private to), generates the slug, and returns aconnectLinkfor a private toolkit.upsert()is deprecated and logs a warning once per process; it keeps working.
API-key auth schemes accept additionalFields.genericId with a required displayName and optional description to collect the value used by {{generic_id}} headers.
- d2d4148:
composio.triggers.create()acceptstype('webhook'or'poll', for a trigger that supports both) andpollingInterval(minutes between polls, which wins overtriggerConfig.interval), and returns the instance'stype,fallbackReasonandpollingIntervalalong withtriggerId.composio.triggers.listActive()items carry the same three fields, andgetType()/listTypes()return each trigger type'stype,typesandrequiresWebhookEndpointSetup.
Patch Changes
- e547eb0: Upload local files with the MIME type of their extension
A file uploaded from a local path used to be sent as application/octet-stream whatever it was, so tools that check the file's type, such as Canva's design import, rejected it. The SDK now infers the type from the file name's extension (a .pptx uploads as application/vnd.openxmlformats-officedocument.presentationml.presentation) and keeps application/octet-stream only for missing or unknown extensions. The TypeScript and Python SDKs now use the same extension table, so a file uploads with the same type from either SDK and from the CLI. Files passed as File objects and URLs keep the type they carry.
- 30f8ca1:
getExtensionFromMimeTypenow mapstext/csvtocsvfrom its table, matching the Python SDK. The returned extension is unchanged. - f6368e0: Add the missing
experimentaloption to theToolRouterAuthorizeFntype.session.authorize()already acceptedexperimental: { accountType, aclConfigForShared }at runtime, but sessions returned bycomposio.create()andcomposio.use()rejected it at compile time.
0.27.0
Minor Changes
- c2bbfa8: Add session hooks. A hook can block a tool call before it runs, or block its result before the agent sees it.
create() and update() accept hooks. On update(), hooks replaces the whole list and null removes every hook. hooks cannot be combined with experimental.sessionConfigId.
const session = await composio.create('user_123', {
hooks: [
{
type: 'before_execute',
id: 'no_external_email',
name: 'No external email',
appliesTo: { toolkits: ['gmail'] },
handler: {
type: 'condition_check',
condition: 'Sending email to anyone outside example.org',
action: 'block',
},
},
],
});
A blocked call comes back from session.execute() and session.executeMeta() with resultType: 'blocked', empty data, the hook's message in error, and blockReason. Provider integrations hand it to the agent as a failed call with that message. Every result also carries hookResults when a hook applied.
session.proxyExecute() and ctx.proxyExecute() now return resultType: 'completed' or resultType: 'blocked'. A blocked request has no HTTP response, so TypeScript code that reads status has to check resultType first.
0.26.0
Minor Changes
- e08c84f: Requires
@composio/client2.0.0-rc.18. The SDK now hands the API client its credential as the client'sauthoption and its organization and project asscope, instead of placing them in default headers. TheapiKey,userApiKey,orgApiKey,orgIdandprojectIdoptions, their environment fallbacks and the credentials sent on each request are unchanged, with one exception: withapiKey: nulland only an organization API key (theorgApiKeyoption,COMPOSIO_ORG_API_KEY, or anx-org-api-keydefault header), every request now carriesx-org-api-key, and so do trigger channel authorization andsession.mcp.headers. Before, only the organization-owner operations did, and every other request went out without a credential.
Credential and scope headers in defaultHeaders or createSession({ headers }) keep working, but the SDK folds them into its own options instead of forwarding them: an x-user-api-key or x-org-api-key entry becomes the credential every request carries, an x-api-key entry becomes the project key, and x-org-id / x-project-id entries become orgId / projectId. getConfig() reports the folded values (for example apiKey: null and userApiKey for an x-user-api-key entry) and no longer lists those entries under defaultHeaders. Setting more than one of x-api-key, x-user-api-key and x-org-api-key now throws a ComposioError; the API rejected every such request.
On the client returned by getClient(), apiKey, userApiKey and orgApiKey are read-only and deprecated (read the keys from getConfig(), or authMode and scope from the client), and a per-call headers option can no longer name a credential or scope header. The API client no longer reads the environment itself: the SDK still honours COMPOSIO_ALLOW_INSECURE_HTTP=1, and no longer applies COMPOSIO_CUSTOM_HEADERS; pass defaultHeaders instead.
The deprecated customConnectionData now requires val.access_token for S2S_OAUTH2, as the API does.
- 57de614: Requires
@composio/client2.0.0-rc.19. The SDK forwards the API client's log lines through aConsole-shaped object instead of the client's removedLoggerinterface; what is logged, and at which SDK level, is unchanged. With rc.19, the client returned bygetClient()no longer hasapiKey,userApiKey,orgApiKeyorlogger, and itsbaseURL,maxRetries,timeoutandlogLevelare read-only: read the keys fromgetConfig(), and derive a client withwithOptions()to change the others.
Patch Changes
- 9d26fb8: Fold OpenAPI
nullableinto the type in strict tool schemas
toStrictJsonSchema no longer passes OpenAPI nullable through. Anthropic strict tool use rejects it on an object schema with a 400 for the whole request. A node with nullable: true now accepts null through its type (["object", "null"]) or a null branch, matching how the tool's arguments are validated, and the rewrite is reported as a nullable-converted change. nullable: false is removed as an unsupported-keyword-stripped change. omitNullToolArguments now keeps a null for a property marked nullable: true, as it already does for one whose type includes null.
- 3dd9a2c: Strip string
formatvalues that OpenAI structured outputs rejects from strict tool schemas
toStrictJsonSchema now removes a format on a string schema unless it is one of date-time, time, date, duration, email, hostname, ipv4, ipv6, or uuid. OpenAI rejects any other string format in strict mode with a 400 for the whole request, so a single tool with format: "uri", a custom format such as repo.nwo, or the format: "path" that file uploads add made every strict request fail. The removal is reported as an unsupported-keyword-stripped change. Formats on number and integer schemas are kept, since the API does not check them.
- 04fdb41: Check a string tool parameter as base64 only when its
contentEncodingisbase64.format: "binary"(raw octets in OpenAPI) and other encodings such asbase16were validated as base64, so the Vercel, LangChain, LlamaIndex, and Claude Agent SDK providers rejected tool calls with plain text or hex in those fields, and the schema sent to the model described them ascontentEncoding: "base64". Those fields are now plain strings.contentEncoding: "base64"keeps its check, andformat: "byte"stays unchecked. - be12ce1: Warn once per toolkit version when the API reports it as deprecated through the
Composio-Deprecated-Toolkitsresponse header. The warning names the version, the sunset date and how to pin a newer version. Silence it withlogLevel: 'error'orCOMPOSIO_LOG_LEVEL=error. - Updated dependencies [f119f05]
- Updated dependencies [04fdb41]
- @composio/json-schema-to-zod@0.4.0
0.25.0
Minor Changes
- 79c2d1d: Requires
@composio/client2.0.0-rc.17. The SDK now reports itself to the API client through the client'sidentityoption instead of default headers. The headers sent with each request are unchanged, with one exception: on Cloudflare Workers and Vercel Edge with Node.js compatibility enabled,x-client-runtimenow names that runtime instead ofnodejs, and the polyfilled Node.js version is no longer sent asx-runtime-version. AcreateSession()clone no longer copies these headers into itsdefaultHeaders.
The API client owns these headers, so defaultHeaders and createSession({ headers }) now reject x-client-provenance, x-client-version, x-client-library, x-client-library-version, x-client-language, x-client-runtime, x-sdk-version, x-source, x-framework, x-runtime and x-runtime-version with a ComposioError from @composio/client. The SDK used to overwrite such entries silently.
A custom provider whose name cannot be sent as a header value (anything other than printable ASCII with no leading or trailing whitespace) is reported as unknown in x-framework.
- 40546c3: Add experimental support for tool calls that need the user's approval.
Sessions accept a requireApproval list next to the toolkits, tools and tags filters on create() and update(). A call to a matching tool doesn't run: session.execute() and session.executeMeta() throw ComposioToolInputRequiredError with the questions on inputRequests. To answer, repeat the same call with the user's answers in inputResponses and the error's requestState:
const session = await composio.create('user_123', {
tools: { gmail: { requireApproval: ['GMAIL_SEND_EMAIL'] } },
});
try {
await session.execute('GMAIL_SEND_EMAIL', args);
} catch (error) {
if (!(error instanceof ComposioToolInputRequiredError)) throw error;
const inputResponses = await promptUser(error.inputRequests);
await session.execute('GMAIL_SEND_EMAIL', args, {
inputResponses,
requestState: error.requestState,
});
}
promptUser is a placeholder for your application's consent UI. Display each request, wait for the user's response, and return the answers keyed by request ID. Forward decline and cancel responses unchanged.
experimental.noElicitationSupportFallback ('deny' or 'allow') sets what happens to such a call when the session's MCP client can't ask the user.
session.executeMeta() now takes these answers as its third argument, so its request options move to the fourth.
The Python SDK gains the same require_approval lists, experimental.no_elicitation_support_fallback, and input_responses and request_state on session.execute() and session.execute_meta().
Patch Changes
- f9a972b: Update the owned API client to
@composio/client@2.0.0-rc.16. The SDK's public API and runtime behavior are unchanged. 04cd5c4: Fix the trigger subscription lifecycle and contain errors from trigger handlers.
triggers.unsubscribe()now closes the realtime connection, so a Node process can exit once it has unsubscribed. A latertriggers.subscribe()opens a new connection.triggers.unsubscribe()before anysubscribe()no longer fetches realtime credentials or creates a client.- Concurrent
subscribe()calls share one connection, andunsubscribe()cancels a subscription that is still connecting, so it never opens a connection or delivers events afterwards. - A rejected promise from an
asynctrigger handler is logged like a synchronous throw instead of escaping as an unhandled rejection that ends the process. Handler failures log the error's message rather than{}.
0.24.0
Minor Changes
- 59935c0: Add
session.executeMeta()to run a Composio meta tool (COMPOSIO_*) within a session. It takes a meta tool slug and optional arguments, and returns the same result assession.execute(), includingresultType. Likesession.execute(), it throwsComposioToolInputRequiredErrorwhen the tool needs user input and is not retried. The newToolRouterSessionMetaToolSlugtype lists the accepted slugs.
The Python SDK gains the matching session.execute_meta() and ToolRouterSessionMetaToolSlug.
Patch Changes
- fd59eba: Update SDK and provider dependencies to compatible releases. Accept Anthropic SDK 0.132 and OpenAI Agents 0.20 in provider peer ranges, and add Pi coding-agent 1.x to the experimental provider's supported peer range.
- 79b4912: Update the owned API client to
@composio/client@2.0.0-rc.14. OAuth connection data types now accept anullid_token. Session tag filters accept thecreateHintandupdateHinttags. The experimentalinstant.returnPricesInSearchSession option returns each Instant tool's price in Session search results, undertoolkitConnectionStatuses[].instantAccount.prices.composio.mcp.generate()now warns once that its URLs rely on the deprecatedinclude_composio_helper_actionsquery parameter; switch to a Session's MCP endpoint. - 58bcde8: Add a
proxyExecutesession option.composio.sessions.create(userId, { proxyExecute: true })exposes theCOMPOSIO_PROXY_EXECUTEmeta tool, which lets the agent call a toolkit's API directly with the user's connected account. A boolean is shorthand for{ enable: boolean }.session.update()accepts the same option, andnullremoves the stored value.proxyExecute: falsealso turns off the sandboxproxy_execute()helper, and the API rejects it at creation together withsandbox.enableProxyExecution: true.
0.23.0
Minor Changes
- 55ed9e2: Update the owned API client to
@composio/client@2.0.0-rc.11.
A session tool can now ask for user input, such as an approval, instead of running: the API answers the call with result_type: "input_required". session.execute(), session.proxyExecute(), provider-wrapped session tools, and the execute / proxyExecute helpers passed to custom tools throw the new ComposioToolInputRequiredError in that case. A local custom tool whose body makes such a call lets the error through instead of returning it as a failed result. The error carries the questions on inputRequests and the opaque request_state on requestState. requestState is continuation state, so it is a non-enumerable property: read it as error.requestState, and console.error(error), util.inspect(error) and JSON.stringify(error) leave it out. Nothing was executed and the call is not retried. The SDK does not submit answers yet.
Every session tool that ran reports result_type as completed or failed, and a failed execution can carry a null or empty error. session.execute() and the custom tool execute helper return it as the new resultType, which is always present; read it rather than error to tell a failure from a success. Provider-wrapped session tools, provider tool calls bound to a session, and the merged COMPOSIO_MULTI_EXECUTE_TOOL result set successful from it alone, so a failure without error text is no longer reported as successful. error is returned as the API sent it. A session execute answer without result_type, or with a value this SDK does not know, throws ValidationError instead of being read as a success or a failure.
A COMPOSIO_MULTI_EXECUTE_TOOL batch that mixes local custom tools with remote tools now throws ComposioToolInputRequiredError when the remote half needs user input, as an all-remote batch already did. It used to report the input request as a failure message on each remote tool, without inputRequests or requestState. Local tools in that batch have already run by then, and their results are discarded by the throw.
Breaking changes:
ToolRouterSessionConfig(session.config, the result ofsession.update()) andToolRouterSessionConfigHistoryConfig(session.listConfigHistory()) are now the client's own config types.instantis always present (falseor the policy object) instead of optional.- In those config types,
toolkitsand eachtoolsentry can be a{ require_approval }-only object, so a check forenabledordisabledno longer covers every case.tagscan carryrequire_approval, and the config can carryproxy_execute. - The session config is returned as the API sent it. The SDK no longer validates
instantat runtime or removes apremium_usagekey. ToolRouterSessionExecuteResponserequiresresultType. A customToolCallSessionpassed to a provider must return it fromexecute(), becausesuccessfulis no longer derived fromerror.Removed the unused
ToolRouterInstantResponseSchemaandToolRouterInstantResponseexports. UseToolRouterSessionConfig['instant']for the Instant policy the API returns.- ec55dd1: Add
userIdtotools.proxyExecute(). It is sent asuser_id, which projects with 2FA enabled check against the connected account and may require. Python'stools.proxy()takes the same value asuser_id.
- ec55dd1: Add
Patch Changes
- 67e80e3: Update the owned API client to
@composio/client@2.0.0-rc.9. - a7b4943: Send product identity, product version, language, and runtime version with API requests. Identify installed core and slim packages separately while preserving existing telemetry headers.
- 077ceb3: Fix tool schemas rejected by OpenAI and Anthropic when a parameter uses
anyOf,oneOf,allOf,$ref, or similar keywords. The converted schema is aZodObjectagain, so the LangChain, Vercel, LlamaIndex, and Claude Agent SDK providers send tool parameters with a top-leveltype: "object". Patterns with escapes such as\_or\:no longer fail every call to the tool. - e3999c4: Stop retrying session tool executions and proxied calls.
session.execute(),session.proxyExecute(), provider-wrapped session tools, and theexecute/proxyExecutehelpers passed to custom tools no longer retry after a timeout, connection error, or 408/409/429/5xx response, so a retry can no longer repeat a side effect such as sending the same email twice. This matchestools.execute()andtools.proxyExecute(). - 8c7e40a:
RemoteFile.save()without a path no longer rejects ordinary file names. Names with characters Windows reserves, such asreport_2026-09-29T10:30:00.csvorWhat is this?.png, are saved with those characters replaced by_. Names longer than 128 bytes are truncated with their extension kept, and reserved device names such asNULget a_prefix. A name changed this way also gets a short digest of the original before its extension (What is this_-9c68adf2da8b6e8d.png). Default saves create a new file exclusively; if the destination exists, a copy number is added before its extension. Repeated default saves therefore return distinct paths and preserve earlier downloads. Names with a NUL byte or no usable basename are still refused. - d9f6291: Tool schema
patternandpatternPropertiesregexes now run on a linear-time engine (RE2, viare2js), so a hostile pattern such as^(a+)+$can no longer hang argument validation. Apatternthat needs lookaround still runs on the native engine when a static check shows it cannot backtrack catastrophically, on input up to 1000 characters; otherwise it is left unenforced. ApatternPropertieskey that needs lookaround or a backreference now fails conversion with anInvalidPatternError(reasonunsupported). Patterns now match astral characters (emoji) as single characters, as JSON Schema's Unicode regex dialect does. - 48d3559: Fix optional enum and const parameters under strict mode. A typed enum such as
{ "type": "string", "enum": ["asc", "desc"] }was widened by addingnullto itstypeonly, so the enum still rejectednulland the model could not omit the parameter. Such schemas are now wrapped whole inanyOfwith anullbranch, as aretypebesideanyOfand$refwith sibling keywords.omitNullToolArgumentsnow keeps anullonly when every keyword of the tool's schema accepts it, so anullthat anenum,const,$refsibling orallOfrejects is treated as an omitted argument. Schemas whose only obstacle tonullistypeoranyOfare emitted exactly as before. A tool whose schema holds a$refinto a property that wrapping moves is reported inunsupportedand sent without strict mode. Null checks remember their answer per schema node and are bounded in depth and work, so a schema whose definitions fan out through shared references stays cheap. - Updated dependencies [077ceb3]
- Updated dependencies [d9f6291]
- @composio/json-schema-to-zod@0.3.4
0.22.0
Minor Changes
- e7580cf: Align session creation and updates with
instant.return_instant_charge, exposeinstantChargeon execution results, and rename search account metadata toinstantAccount. Useinstant_accountfor explicit account selection. - ae3c069: Expose the exact Instant charge as
instantChargein project usage summaries and asmetadata.instant_chargein tool log metadata. - e182bc8: Remove the deprecated OpenAI Assistants API helpers from
OpenAIProvider:handleAssistantMessage,waitAndHandleAssistantToolCalls, andwaitAndHandleAssistantStreamToolCalls. OpenAI shut down the Assistants API on August 26, 2026, so these helpers could no longer complete a run. UseOpenAIResponsesProviderfrom@composio/openaiwith the Responses API instead.
Patch Changes
- f478a3d: Keep
ConnectionRequest.statusin sync withwaitForConnection(). The request now reportsACTIVEonce the connection completes, or the terminal status (FAILED,EXPIRED,REVOKED) when it fails, matchingtoJSON()and the Python SDK. - f478a3d: Restore telemetry for
ConnectionRequest.waitForConnection().telemetry.instrument()now also instruments async methods defined directly on plain objects, such as the ones returned bycreateConnectionRequest(). - 485c09d: Refresh runtime dependencies and support Anthropic SDK 0.127 in the Anthropic provider.
0.21.0
Minor Changes
- 461c6c3: Add experimental
premiumUsagesupport when creating and updating Tool Router Sessions. - 0833c1b: Expose
hostedAccount.allowedToolSlugsonsession.search()toolkit connection statuses for toolkits served by a Composio hosted account. - de5e3f6: Add experimental support for saved Session configs.
composio.sessionConfigs.list()andcomposio.sessionConfigs.get()read the project's savedsc_…configs, andexperimental.sessionConfigIdoncomposio.sessions.create()starts a session from one. CombiningsessionConfigIdwith inline access fields now fails before any request: on create withtoolkits,tools,tags,experimental.customToolsorexperimental.customToolkits, and onsession.update()withtoolkits,toolsortags(includingnull). TypeScript reports the mix at compile time and the SDK throwsValidationErrorat runtime; other invalid inputs keep throwingZodError.session.experimental.sourceSessionConfigexposes the last config applied to the session aftercreate(),sessions.use()andupdate(). A 409 whileupdate()applies a config now says that the session or the config changed and to re-fetch and retry, instead of reporting a stale version.
Patch Changes
- 3721d04: Validate the server-supplied mount path before
RemoteFile.save()turns it into a filename. AmountRelativePathof"",".","sub/.","foo/.."or".."made the default save path equal the download directory or its parent, which surfaced as an unhandledEISDIRfromwriteFileSyncafter the directory had already been created. These now throw aValidationErrornaming the offending mount path, before anymkdiror write. An explicitpathpassed by the caller is unaffected.
The new safeBasename helper applies the filename safety checks used by the Python SDK: both / and \ count as separators, and NUL or control characters, Windows-reserved characters and device names, trailing spaces or dots, invalid Unicode and names over 128 UTF-8 bytes are rejected. RemoteFile.filename now also splits on both separators, so a Windows-style mount path reduces to the same display name on every platform.
Drive-relative paths such as C:report.txt reduce to report.txt. Whitespace stripping follows Python rules, preserving U+FEFF. Both SDKs also reject trailing dots exposed by stripping Unicode whitespace.
- 5ec0bdf: Validate the default destination in
RemoteFile.save()before downloading content. Invalid mount paths now raiseValidationErrorwithout a network request, even when the download would fail. - de5e3f6: Remove experimental annotations from the top-level Session config read methods. Applying a config and reading its source metadata remain under
experimental. - 5d07582:
session.update()no longer sendsexpected_config_versionby default. Since 0.20.0 it sent the session's last observedconfigVersionon every call, and the API rejects that field with a 400 (Unrecognized key(s) in object: 'expected_config_version'), so every defaultupdate()failed. The default is now last writer wins. PassexpectedConfigVersion(for examplesession.configVersion) to make an update conditional where the API supports it;expectedConfigVersion: falseis the same as omitting it.
0.20.0
Minor Changes
- a4a40a1: Fix project API key resolution so the SDK never sends a Composio user API key (
uak_..., as stored bycomposio login) as thex-api-keyproject credential. When that stored key is the only candidate, the constructor now throws a redactedComposioAPIKeyKindErrorthat explains the mismatch instead of making requests that fail with 401.apiKey: nullnow disables project-key authentication entirely, including theCOMPOSIO_API_KEYand~/.composio/user_data.jsonfallbacks, and is accepted when the instance holds another credential:userApiKeyororgApiKey(explicit or from their environment variables), or anx-user-api-keyentry indefaultHeaders. Requests then carry only that credential. Malformed or unexpectedly shaped user config files produce a diagnostic that names the file without echoing its contents, and cloned instances keep the credential they were resolved with instead of re-reading the environment. Code that resolves the key withapiKey: process.env.COMPOSIO_API_KEY ?? null(or any expression that yieldsnullwhen the variable is unset) is affected: it used to fall back to the environment and the CLI config file and now throws unless another credential is configured; omitapiKey(or passundefined) to keep the fallbacks. WithapiKey: null, anx-api-keyentry indefaultHeadersis rejected as well, including oncreateSession()clones: pass the project key asapiKeyinstead of a raw header. - 6c56b73: Add
userApiKeyandorgApiKeytoComposioConfig. Both are forwarded to the underlying API client, which sends each one only on operations whose security scheme requires it (organization, consumer, and user-scoped endpoints reached throughgetClient()), never alongside the project key. They fall back toCOMPOSIO_USER_API_KEYandCOMPOSIO_ORG_API_KEY. A projectapiKeyis still required unless it is set tonull, which opts into user-only authentication. 6c56b73: Expose the rest of the owned client surface on the
Composioclass:composio.webhooks.subscriptions(list,get,set,update,delete,rotateSecret,listEventTypes) andcomposio.webhooks.endpoints(list,get,create,replace,update).composio.triggers.setWebhookSubscription()now delegates to the same upsert aswebhooks.subscriptions.set(). Its behaviour for well-formed API responses is unchanged; malformed responses are now rejected with aValidationErrorinstead of being read leniently.composio.logs.search()andcomposio.logs.get()for tool-execution logs.composio.connectedAccounts.revoke(), which surfaces the API's 400/409 asComposioConnectedAccountRevocationNotSupportedError/ComposioConnectedAccountNotRevokableError.connectedAccounts.refresh()is marked@deprecated(the endpoint is deprecated upstream).composio.toolkits.getMany(slugs)andcomposio.toolkits.changelog().session.listConfigHistory()on sessions.composio.experimental.usage.summary()andcomposio.experimental.usage.breakdown()(experimental, shape may change).composio.toolkits.recommendScopes(toolkitSlug, { tools, ... })andcomposio.toolkits.listGrantContexts(toolkitSlug)for OAuth scope recommendations (the API marks both beta).composio.connectedAccounts.completeAuth({ userId, sessionUri }), which completes a deferred OAuth connection after your OAuth callback verifier has confirmed the user's identity.composio.keyring.listTransferKeys(), which returns the public JWKs of the organization's customer-managed keyring.composio.experimental.customToolkits(upsert,sync,delete) for project-owned custom toolkits (in pilot, shape may change).CIMD_OAUTHjoinsAuthSchemeTypes.triggers.listActive()returns{}forstateandtriggerConfigwhen the API sendsnull.ToolkitAuthFieldgainsuserVisible(fromuser_visible) andToolkitAuthConfigDetailsgainsrequiredScopes(fromrequired_scopes), both omitted when the API does not send them.@composio/clientmoves from the old autogenerated client to the new handrolled client. The API removedvalidate_credentialsfrom the connected-account refresh, soconnectedAccounts.refresh()now ignoresvalidateCredentialsand logs a warning when it is set.loggerandlogLeveloptions onnew Composio({...}).loggeraccepts any{ error, warn, info, debug }sink (console, pino, winston, ...) and receives the SDK's formatted, credential-redacted output;logLevel('silent' | 'error' | 'warn' | 'info' | 'debug') overridesCOMPOSIO_LOG_LEVEL. The owned client's runtime deprecation warnings (responseDeprecation/Sunsetheaders and deprecated request inputs) are now routed through that SDK logger instead ofconsole. The client's per-request lifecycle logs are emitted only at'debug'.tools.get/getRawComposioToolssend the API'squeryparameter in place of the deprecatedsearchwire parameter; the SDK's publicsearchoption is unchanged.
a4a40a1: Sessions now export their MCP config from the auth context the session request was actually made with: the project key as
x-api-keywhen one is configured, otherwise the user API key (userApiKeyor thex-user-api-keydefault header) asx-user-api-key, plusx-org-id/x-project-idwhen the instance is scoped. No other default header and no ambientCOMPOSIO_API_KEYis ever copied. The headers are only attached when the MCP URL shares the origin of the configured API base URL (whatever its scheme). Any other destination (a different origin, an opaque origin such as adata:URL, or a URL that does not parse) never receives them: withmcp: true,create()/use()throwComposioMCPDestinationError, which names both origins and never includes a key; withoutmcp: truethe session is returned withsession.mcp.headersempty and a warning naming both origins is logged, so native tools keep working. The SDK never connects to the MCP URL itself and does not follow redirects for it. Trigger subscriptions (Pusher channel auth) follow the same rule instead of falling back to the environment when the project key is disabled.
ComposioConfig gains orgId and projectId: the organization and consumer project nano IDs, sent together as the x-org-id / x-project-id headers on every request and with the session MCP config. They may also be supplied through defaultHeaders; a half-configured or disagreeing scope throws ComposioScopeConfigError. Without a scope, a user API key keeps addressing the API default project.
session.update() now sends the session's last observed configVersion as the expected_config_version precondition by default and never retries that request, so a concurrent change surfaces as ComposioSessionConfigConflictError (HTTP 409; re-fetch the session, then retry) while the local session object stays unchanged. Pass expectedConfigVersion to send another version or expectedConfigVersion: false to opt out (last writer wins). Every policy block (toolkits, tools, tags, authConfigs, connectedAccounts, preload, manageConnections, multiAccount, search, execute, experimental) accepts null to remove the stored override, manageConnections.callbackUrl: null removes only the stored callback URL, multiAccount.maxAccountsPerToolkit: null removes the stored maximum, and an empty toolkit allowlist (toolkits: []) is sent as-is so it denies every app toolkit.
- 6c56b73: Replace the old autogenerated
@composio/clientwith the new handrolled client.
0.19.0
Minor Changes
- efc2e52: Keep TypeScript realtime subscription errors inside the SDK logging boundary so an asynchronous Pusher subscription failure cannot escape as an uncaught exception. The full subscription error payload is now logged, the success message is logged only once Pusher confirms the subscription, and
PusherService.subscribe/Triggers.subscribeaccept an optionalonSubscriptionErrorcallback so applications can react to subscription failures programmatically. - 4b5920b: Add
session.ensureConnected(toolkit, options?): it returns immediately when the session already resolves an active connection (or the toolkit is no-auth), and only when needed starts the authorization flow viasession.authorize()and waits for the new connection to become active. This preventsauthorize()from spawning duplicate pending connections for toolkits that are already connected. Thesession.execute()accountoption is now documented as accepted on every project — on single-account projects the identifier must match one of the session's active connections for the toolkit (matching the API behavior). - c7843d8: Expose the server-side session configuration on sessions and return it from
update().session.confignow carries the toolkit/tool allowlists, tags, auth configs, connected accounts,manage_connections, preload and sandbox settings the API returned for the session (fromcreate(),use()and after everyupdate()), andsession.update()resolves to that updated config instead ofvoid. Previously the onlyconfigreachable on a session object at runtime was the SDK's ownComposioConfig, and reading the live allowlist aftersessions.use(id)required dropping to the raw client.
config is a required member of the Session interface, so objects you construct yourself to satisfy Session (test doubles, wrappers) now need a config value. Callers of SDK-created sessions are unaffected. The read side is the raw API shape (toolkits.enabled, manage_connections), while update() keeps taking the SDK's camelCase input.
Patch Changes
- 62e51e8: Refresh runtime dependencies and extend provider peer compatibility to the latest supported Anthropic and OpenAI Agents SDK releases.
- 7055914: Move published dependency ranges to their current upstream releases: zod 4.5, openai 7.10, typebox 1.3.27, @mastra/schema-compat 1.3.8, and @cloudflare/workers-types 5.20260905.
@composio/anthropicalso accepts@anthropic-ai/sdk0.124 as a peer, the line it is now tested against. - b4b9fc4: Guard schema
patternandpatternPropertiescompilation. A pattern that does not compile or exceeds 1024 characters now fails conversion with anInvalidPatternErrorthat names the offending property path instead of a rawSyntaxError.@composio/coresurfaces that path in theJsonSchemaToZodErrormessage. No backtracking heuristic is applied: a hostilepatternthat backtracks catastrophically remains a known limitation. - d4d3060: Fix
composio.mcp.update()silently dropping parts of the requested configuration. Tool-only updates (allowedToolswithouttoolkits) sent no tools field at all, updates with toolkits sent the deprecated create-timecustom_toolsalias that the update endpoint ignores instead ofallowed_tools, andmanuallyManageConnectionswas forwarded as-is instead of being inverted intomanaged_auth_via_composio(somanuallyManageConnections: truestored the opposite configuration).create()andupdate()now also keep the auth config of a{ toolkit, authConfigId }toolkit entry instead of discarding it, andcreate()sendsallowed_toolsrather than the deprecatedcustom_toolsalias, matching the Python SDK. - 9d0cb2c: Export
readResponseBodyWithLimitandMAX_URL_UPLOAD_SIZE_BYTESso downstream packages can apply the SDK's 100 MiB cap when they download a file from a user-supplied URL. The CLI's tool-input file uploads now use it instead of buffering the whole response. - ba85f4d: Apply the Fetch standard's redirect rules in
ssrfSafeFetch, which following redirects manually meantfetchnever applied: a303now retries as a bodilessGETinstead of replaying an upload's method and body at a result URL, a301/302does the same for aPOST, and307/308keep replaying both. Only301,302,303,307and308count as redirects to follow, so a304or305carrying aLocationis returned to the caller rather than followed. - ba85f4d: Close the IPv6 transition ranges the SSRF guard's address blocklist let through: 6to4 (
2002::/16), Teredo and the rest of2001::/23, local-use NAT64 (64:ff9b:1::/48),100::/64,2001:db8::/32and site-localfec0::/10each carry or reach an arbitrary IPv4 address, so2002:7f00:1::was a public-looking literal for127.0.0.1. IPv4 multicast and the192.88.99.0/246to4 relay range are blocked too. - 85996c4: Drop
Authorization,Proxy-Authorization, andCookiefrom the request headers when the SSRF guard follows a redirect to a different origin, as the Fetch standard does for automatic redirects. Same-origin redirects keep them. - eccb80e: Add an opt-in strict mode to
ssrfSafeFetchthat rejects configured network routes when the connection cannot be pinned to the validated address. - 8bb1d29: Stop reporting every failed tool lookup as
ComposioToolNotFoundError.tools.getRawComposioToolBySlug, and thetools.get/tools.executepaths that call it, now raiseComposioToolNotFoundErroronly when the API answers 404 or 400. Any other failure, such as an invalid API key (401), a server error, or a network fault, raises the newComposioToolFetchErrorwith the client error preserved ascause.toolkits.get(slug)now applies its 404/400 check against the Composio client'sAPIErrorinstead of the OpenAI one, so an unknown toolkit raisesComposioToolkitNotFoundErroras documented. - e9fcbe3: Stop dropping
is_secret,legacy_template_nameandauth_hint_urlfrom toolkit auth config details.transformToolkitRetrieveResponsepassed the auth field groups through unchanged, so the snake_case keys never matchedToolkitAuthFieldSchemaand zod stripped them during validation;auth_hint_urlwas never mapped at all. Fields returned bytoolkits.getConnectedAccountInitiationFields()andtoolkits.getAuthConfigCreationFields()now carryisSecret, which the API documents as the signal for whether a client should mask the input, pluslegacyTemplateName; auth config details returned bytoolkits.get()now carryauthHintUrl. Each of these keys is present only when the API sends it, so spreading a field no longer overwrites a caller's own fallback withundefined. An auth config detail that omits a field group entirely now yields empty lists for that group, matching how the docs pipeline defaults them, instead of failing validation and leaving the other group unusable. - 9a69683: Correct the JSDoc for
tools.getInputandtools.proxyExecute. ThegetInputexample now passes the requiredtextfield and reads the generatedarguments. TheproxyExecuteexample now uses the flatendpoint/method/connectedAccountIdshape and explains that a relative endpoint is appended to the toolkit's base URL, which can already include a path. Thetools.executeexample shows where to find the version to pin. - Updated dependencies [b4b9fc4]
- @composio/json-schema-to-zod@0.3.3
0.18.1
Patch Changes
- 8a56383: Fix: automatic S3 file downloads are now capped at 100 MiB (configurable per call) to prevent memory exhaustion from oversized or streaming responses.
- 7420927: Fix custom toolkit child slug mapping: reject response tools that have local handles but no exact toolkit match instead of silently dropping them or binding another toolkit's handler, derive bare-slug ambiguity from local definitions, and only reuse a same-toolkit bare alias in customToolkits().
- 1d31c80: Redact credential-shaped values at the SDK log boundary.
- 95f9d32: Expose the runtime-conditional SSRF-safe fetch helper for protected URL upload consumers.
- 0d28bef: Map file-download transport failures to the SDK error contract and bound streamed response bodies.
- 52efb5b: Fix trigger subscriptions ignoring the
authConfigIdfilter. - Updated dependencies [ab289d6]
- @composio/json-schema-to-zod@0.3.2
0.18.0
Minor Changes
- 04817cb: Fix strict-mode tool schemas for OpenAI structured outputs. Strict normalization now applies OpenAI's contract at every depth (nested objects,
anyOfbranches, array items, inlined$ref/$defs): every object lists all of its properties inrequiredand setsadditionalProperties: false, so tools with nested or optional parameters no longer produce schemas the API rejects with a 400. Optional parameters are no longer dropped: they stay available and are widened to acceptnull, the emulation of optional fields OpenAI documents, and the strict providers drop anullargument the tool's own schema does not accept before executing the tool. Tools whose schema strict mode cannot express (objects with arbitrary keys,allOf,prefixItems, unresolved$refs) are sent without strict mode with a warning naming the tool and path, instead of being narrowed.@composio/coreexports the newtoStrictJsonSchema()andomitNullToolArguments()utilities;removeNonRequiredPropertiesis unchanged for other callers. The PythonOpenAIResponsesProvidergains a matching opt-instrict=Trueconstructor flag that also emitsstrict: trueon the wrapped tool.
Patch Changes
- 449f4e1: Block automatic uploads when a sensitive directory or file name is hidden by symlink resolution.
- 9545806: Bound the best-effort telemetry requests with a timeout so a stalled telemetry endpoint cannot leave an SDK call pending indefinitely.
- db7b576: Declare Node.js 22.22.3 as the minimum supported runtime for every published TypeScript package so package managers surface incompatible runtimes before users encounter ESM loading failures.
- fe66cbe: Omit empty-string file-uploadable arguments from tool execution requests instead of forwarding them to the backend, which rejected them with "Input should be a valid dictionary or instance of FileUploadable". This now also applies when
dangerouslyAllowAutoUploadDownloadFilesis off, and with it on an empty value is no longer attempted as an upload. - c0f1609: Fix three ComposioError subclasses (ComposioToolVersionRequiredError, JsonSchemaToZodError, JsonSchemaRefResolutionError) that omitted their
this.nameassignment and therefore reportednameas 'ComposioError' instead of their own class name, mis-grouping distinct error types in error telemetry. - d544006: Close a DNS-rebinding window in the SSRF guard: the address validated by
assertSafeFetchTargetis now the addressssrfSafeFetchconnects to, so a hostname is no longer resolved a second time between the check and the connection. Each redirect hop is re-validated and re-pinned. The request still carries the original hostname inHostand TLS SNI, so certificate verification is unchanged. Hops whose effective dispatcher is a configured route — a caller-supplieddispatcher, a globalProxyAgent/EnvHttpProxyAgent, orNODE_USE_ENV_PROXYenv-proxy mode — keep the pre-flight check only, mirroring the Python guard's documented proxy residual. - Updated dependencies [db7b576]
- @composio/json-schema-to-zod@0.3.1
0.17.0
Minor Changes
- 760f8d0: Allow OpenAI and Anthropic provider tool-call helpers to execute through a supplied Tool Router session. Session meta-tools now retain their session context while provider argument normalization remains intact; existing user-ID calls continue to use direct execution. Anthropic helper failures now preserve their error text in
{ error }results without changing successful payloads. Custom provider subclasses overridingexecuteToolCallorhandleToolCallsmay require updates because these methods now accept session targets.
Patch Changes
- 6ba9179: Validate the URLs that come from API responses before fetching them. Tool-execution downloads (
s3Url), S3 presigned uploads (new_presigned_url), Tool Router session file downloads (RemoteFile.buffer()/blob()/text()/save()) and session file uploads (upload_url) now go through the same SSRF guard that already covered user-supplied URLs, so a response naming a private, loopback, or link-local address is refused instead of fetched. Redirect hops are re-validated. Edge runtimes keep their current behavior: session file transfers are not blocked there, since a Worker cannot resolve DNS to check and itsfetchdoes not originate inside the caller's network.
0.16.0
Minor Changes
- 5e57815: Keep free-form object roots,
patternProperties, andadditionalPropertieswhen parsing a tool schema.
ToolSchema.parse used to reject a bare { "type": "object" } root, drop root patternProperties as an unknown key, and reject a root additionalProperties written as a schema instead of a boolean. Free-form roots now parse successfully, and both constraints survive parsing exactly as written. The public ToolSchema type now makes properties optional to reflect those valid property-less object schemas.
This matters downstream. Every provider reads inputParameters after parsing, so a tool that declares dynamic keys had those rules stripped before the model ever saw them.
An omitted additionalProperties still stays omitted. The parser does not invent a value, because each converter decides its own default.
What no longer works
Parsing no longer fails on a schema-valued root additionalProperties.
const tool = ToolSchema.parse({
slug: 'MY_TOOL',
inputParameters: {
type: 'object',
properties: { name: { type: 'string' } },
additionalProperties: { type: 'number' },
},
// ...
});
// before: parsing failed, because only a boolean was accepted
// now: tool.inputParameters.additionalProperties is { type: 'number' }
What to do instead
Nothing, if you only ever passed boolean values. That case is unchanged.
If your code assumed inputParameters never carries patternProperties, or that additionalProperties is always a boolean, widen that assumption. Both keywords can now appear, and additionalProperties can be a boolean or a schema object.
Patch Changes
- a2f6b96: Add
type: "object"to nested JSON Schema nodes that carrypropertieswithout an explicit type, so tool schemas work with strict OpenAPI 3.0 consumers like Google Gemini. - c625edc: Reuse fetched tool schemas when provider-wrapped tools execute to avoid a redundant retrieval request.
- Updated dependencies [5e57815]
- @composio/json-schema-to-zod@0.3.0
0.15.0
Minor Changes
- 1503786: Replace the loose JSON Schema property type with a recursive, type-safe definition.
JSONSchemaProperty (re-exported from @composio/core and reachable through
Tool.input_parameters / Tool.output_parameters) is now a concrete recursive
interface instead of effectively any. Runtime behavior is unchanged, but
consumer code that indexed into it without narrowing (for example
schema.properties.foo.type or schema.default.someField) may see new type
errors: properties entries are now possibly undefined and default /
enum values are unknown. Narrow with optional chaining or explicit type
guards when upgrading.
Patch Changes
- 2ac6ad3: Bound the background npm version check so registry outages cannot leave the request pending indefinitely.
- 5105612: Match sensitive upload path segments using the target filesystem's actual case sensitivity so case-insensitive mounts cannot bypass the denylist without over-blocking distinct paths on case-sensitive mounts.
- 051c8c5: Redact secrets that appear inside JSON payloads in telemetry error text. The key/value rule required the separator to follow the key name directly, so a serialized body such as
{"api_key": "..."}— the shape error messages usually carry — was sent unredacted. - e5c9ada: Refresh the OpenAI runtime dependency to version 7.
- ecd0861: Release unread response bodies on the paths the SDK knowingly abandons: cancel every intermediate redirect body in
ssrfSafeFetch, and the response body before throwing on!response.okin both URL-upload call sites, instead of leaving them for the garbage collector to reclaim. - 2a6a051: Remove the unused internal
isNewerVersionhelper. - Updated dependencies [1503786]
- @composio/json-schema-to-zod@0.2.2
0.14.1
Patch Changes
- 577a3d4: Replace the backtracking leading/trailing-slash-trim regexes in the Cloudflare Workers/Edge platform path helpers with index-walk loops, closing a polynomial-time regular expression denial-of-service (CodeQL js/polynomial-redos) on long runs of slash characters. Output is unchanged for every input.
- 503b50a: Refresh runtime dependencies across the TypeScript SDK packages.
- 2f63fe5: Guard Tool Router session URL uploads against SSRF, revalidate redirect targets, and enforce a streamed 100 MiB response limit across TypeScript URL upload paths.
0.14.0
Minor Changes
- fc17c37: Export the sensitive-file-upload denylist guard from the package root so downstream packages share one implementation:
assertSafeFileUploadPath,isBlockedSensitiveFileUploadPath, andBUILTIN_FILE_UPLOAD_PATH_DENY_SEGMENTS. The guard now routes its filesystem access through the internal#platformabstraction (adding arealpathSyncplatform method), so it is edge/workerd-safe and the module carries no staticnode:*imports. Behavior on Node/Bun is unchanged. 20a4711:
triggers.createnow resolves the connection fromuser_idon the backend instead of client-side.- The SDK no longer makes an extra
connectedAccounts.list()call. WhenconnectedAccountIdis omitted, the backend resolves the first active connection for the user and the trigger's toolkit (ordered by most recently created), matching tool execution. - Behavior change:
createno longer throwsComposioConnectedAccountNotFoundErrorfor a missing or invalid connection. That case now surfaces as the backend error from the upsert call.ComposioTriggerTypeNotFoundError(invalid slug) andValidationError(including emptyuserId) are still thrown client-side. - Requires a backend that resolves the trigger connection from
user_idon upsert (ComposioHQ/platform#10932). Self-hosted deployments must be on a version that includes it.
- The SDK no longer makes an extra
Patch Changes
- 7125576: Normalize duplicate JSON Schema
requiredentries before provider tool schemas are emitted. - 58bc93b: Refresh dependency ranges and lockfiles across the workspace.
- 4c3a321: Disable client retries on
tools.executeandtools.proxyExecute. These are non-idempotent writes, so a silent retry after a read timeout could duplicate the side effect (e.g. send the same email more than once). Both now route through a sibling client built withmaxRetries: 0; reads keep the default retry behaviour. - b07fcad: Add an eve provider:
EveProvidermakessession.tools()return eve-nativedefineTools,defineComposioToolsis the replay-safestep.startedresolver, and(ctx, next)hooks can rewrite, deny, or transform Tool Router meta-tool calls.
Preserve successful local-tool results when the remote half of a mixed COMPOSIO_MULTI_EXECUTE_TOOL batch fails at the transport layer, so callers can see which side effects already completed before retrying.
- fa933a6: Fix the
homepagelinks in these packages'package.json. They pointed atgithub.com/ComposioHQ/composio/tree/main/..., but the default branch isnextand nomainbranch exists, so every link 404'd on npm and in editor tooltips. They now point attree/next/.... - 2ef40ce: Treat local file paths that begin with
httpas paths instead of URLs, ensuring that upload allowlist and sensitive-file denylist checks still run. - e78ed31: Execute every parallel tool call in
OpenAIProvider.handleToolCalls. It previously only ran the first tool call in each assistant message, so parallel tool calls (on by default) dropped the rest and left theirtool_call_ids unanswered, failing the next request.
The calls are run sequentially, in the order the model returned them — here "parallel" means the model issued several calls in one turn, not that they execute concurrently — so each tool_call_id is answered exactly once and the tool messages come back in a deterministic order.
Only the first choice is handled. Tool results are fed back into a single assistant turn, so with n > 1 iterating over every choice would run each tool call once per choice and orphan the tool_call_ids from the alternative completions.
a0f37a7: Close two secret/SSRF exposure surfaces in the TypeScript SDK:
- SSRF guard on URL file inputs.
composio.files.upload(url)and automatic file upload during tool execution previously did a rawfetch()on user-supplied URLs with no guard. They now resolve the host and refuse private, loopback, link-local (incl. the169.254.169.254cloud-metadata endpoint), CGNAT, and reserved addresses, reject non-http(s)schemes, and follow redirects manually so each hop is re-validated (blocking a public URL that redirects into internal space). Blocked requests throwComposioBlockedInternalUrlError. Node-only; behaviour for public URLs is unchanged. - Telemetry redaction. Error telemetry previously shipped
error.message/error.stackverbatim. They are now passed through a redactor that strips URL query strings,Authorizationbearer/basic credentials, and secret-likekey=valuepairs (API keys, tokens, client secrets, passwords) before transport.
- SSRF guard on URL file inputs.
820abb9: Resolve toolkit version pins case-insensitively. Version maps are keyed by normalized (lowercase) slugs, but
getToolkitVersionpreviously looked them up with the raw slug, so a pin configured under a different casing (e.g.{ GitHub: '20250101_00' }orCOMPOSIO_TOOLKIT_VERSION_GITHUB) could silently fall back to'latest'. Normalization is now centralized in a singlenormalizeToolkitSlughelper used symmetrically on both the write (map-building) and read (lookup) paths, so the two sides can no longer drift. This mirrors the equivalent fix in the Python SDK.Updated dependencies [58bc93b]
Updated dependencies [fa933a6]
- @composio/json-schema-to-zod@0.2.1
0.13.1
Patch Changes
- 605a726: Add Tool Router session deletion APIs.
0.13.0
Minor Changes
- d17a268: Add the first-class
composio.sessions.create()API while keepingcomposio.create()as an alias, expose the experimental shared-connection ACL patch helper asconnectedAccounts.updateAcl()while keepingexperimental.updateAcl()as an alias, and include SDK docs/source in the published package.
MCP is now opt-in. Sessions return native tools by default; the hosted MCP endpoint is only surfaced on the type when you create the session with { mcp: true }. The default create() / use() now return SessionWithoutMcp (the runtime object is unchanged — session.mcp still exists at runtime — but it is no longer in the type).
Migration: read session.mcp only after creating with { mcp: true }.
d17a268: Surface the resolved workbench config on Tool Router sessions.
Session.workbenchis now populated from the API response (on create/retrieve/attach/update). It exposes the resolved workbench config, e.g.session.workbench?.enable(defaults totrueserver-side).
This lets callers create a session with the remote workbench disabled (workbench: { enable: false }) and detect that state — the foundation for running code in a sandbox you own via the experimental @composio/experimental/workbench helpers.
Patch Changes
- d17a268: Prefer
sandboxfor session code-execution configuration while continuing to accept the existingworkbenchalias. - d17a268: Add
triggers.parse()to parse and optionally verify incoming webhook requests. - d17a268: Add
triggers.setWebhookSubscription()to create or update the project webhook subscription from the TypeScript SDK.
0.12.0
Minor Changes
- a0bef5d: Bump
@composio/clientto0.1.0-alpha.74. - dfd7a08: Add per-request cancellation to public SDK methods via a new
ComposioRequestOptions({ signal?: AbortSignal }) trailing argument, plus a typedComposioRequestCancelledErrorfor detecting caller-initiated aborts.
Without this, a slow tools.get or tools.execute had no way to be cancelled — a 100s search would block the calling agent indefinitely. The new shape:
try {
const tools = await composio.tools.get(
'user_1',
{ search: 'send email', limit: 50 },
{ signal: AbortSignal.timeout(5_000) }
);
} catch (err) {
if (err instanceof ComposioRequestCancelledError) {
return;
}
throw err;
}
The signal is forwarded to the underlying @composio/client fetch. Any abort error (APIUserAbortError, AbortError, or DOMException(name='AbortError')) coming back is normalized to ComposioRequestCancelledError so callers can instanceof-detect cancellation without unwrapping nested causes. Catch-and-wrap paths in tools.execute / tools.getRawComposioToolBySlug / toolkits.get re-throw the cancellation error rather than remapping it to ComposioToolExecutionError / ComposioToolNotFoundError / ComposioToolkitFetchError.
Wired through on:
- Tools: get, getRawComposioTools, getRawComposioToolBySlug, getRawToolRouterSessionTools, execute, executeSessionTool, getToolsEnum, getInput, proxyExecute
- Toolkits: get, listCategories
- AuthConfigs: list, create, get, update, delete, updateStatus, enable, disable
- ConnectedAccounts: list, get, delete, refresh, updateStatus, enable, disable, update
- Triggers: listActive, create, update, delete, enable, disable, listTypes, getType, listEnum
- MCP: create, list, get, delete, update, generate
- ToolRouter (composio.create / composio.use, composio.toolRouter.create / .use) — long-running session-creation paths
- ToolRouterSession: authorize, toolkits, search, execute, proxyExecute, update
### Custom-tool cooperative cancellation
Native tool execution is cancelled by the SDK (the underlying fetch is aborted). Custom tools are different — the SDK can't preempt user-supplied JavaScript. Two affordances are added so callers get sensible behavior anyway:
- Pre-execute signal check: if
signal.abortedis true before the user'sexecuteruns, the SDK throwsComposioRequestCancelledErrorand never invokes user code. - Cooperative signal forwarding: the same
AbortSignalis exposed viaSessionContext.signalfor Tool Router custom tools. Long-running implementations can wirectx.signalinto their ownfetch(or any abortable IO) to abort mid-execution; the resultingAbortErroris normalized toComposioRequestCancelledErrorby the SDK.
import { experimental_createTool } from '@composio/core';
const longRunningFetch = experimental_createTool('LONG_RUNNING_FETCH', {
name: 'Long-running fetch',
description: 'Fetches a URL with cooperative cancellation',
inputParams: z.object({ url: z.string() }),
execute: async (input, ctx) => {
// Pass ctx.signal into fetch so a session.execute(...) abort cancels
// the in-flight HTTP request mid-flight.
const resp = await fetch(input.url, { signal: ctx.signal });
return { result: await resp.json() };
},
});
- 025a657: Drop CommonJS entrypoints and publish the TypeScript SDK packages as ESM-only packages. This is a breaking change within the existing 0.x release line: consumers must use Node.js 22.22.3 or newer. CommonJS callers can only rely on Node's native
require(esm)interop, and the SDK no longer ships custom CommonJS compatibility machinery or.cjsartifacts. - 4b76dbf: Remove the deprecated
uuidfield from the auth config retrieve/list response type.
The platform has removed the deprecated V1/V2 UUID-mirror field from V3 API responses (it was a mirror of the canonical nanoid id). The SDK no longer reads or re-exposes uuid on AuthConfigRetrieveResponse (and therefore on the items of AuthConfigListResponse).
This is technically a breaking change to the SDK response type: consumers should use id instead of uuid. The expectedInputFields field is unaffected — it remains a top-level field on the API response.
Patch Changes
- 552859a: Expose
searchandshowDisabledfilters onauthConfigs.list(). - 23f9053: Replace
chalkwithpicocolorsfor colored error and log output. The two render identically, butpicocolorsis a fraction of the size (~0.8 kB gzipped vs chalk's much larger footprint), shrinking the bundled package. - 507318d: Add a provider-agnostic JSON-schema property-key sanitizer:
sanitizeSchemaPropertyKeys(schema, policy),restoreOriginalKeys(value, mapping),mappingHasRenames(mapping), and theKeyMapping/KeySanitizationPolicytypes.
Some providers constrain the characters and length of tool input_schema property keys and reject the whole request on a single violation. This utility rewrites offending keys to conforming aliases (recursing through properties, array items/prefixItems, the composition keywords allOf/anyOf/oneOf and not/if/then/else, plus additionalProperties/patternProperties/$defs/contains) and records a schema-shaped reverse mapping so the original parameter names can be restored before execution. The constraint is injected as a KeySanitizationPolicy, so the traversal, collision handling, prototype safety, and depth cap stay provider-agnostic. The @composio/anthropic provider now consumes it.
- 6a4cb54: Preserve root
$defs/definitionsblocks on tool parameter schemas and dereference them in the Node file modifier, so auto file upload/download detection works whenfile_uploadableorfile_downloadableis hidden behind an internal$ref. - cbbad15: Improve Zod compatibility at the SDK schema boundary. Custom tools now convert both
zod/v3and Zod v4 schemas to JSON Schema correctly instead of degrading Zod v4 object schemas to empty schemas.@composio/corenow exposesjsonSchemaToZodShapevia@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.shapeout of it. - Updated dependencies [025a657]
- @composio/json-schema-to-zod@0.2.0
0.11.0
Minor Changes
- a94715f: Forward
userIdwhen creating trigger instances so trigger 2FA flows can verify connected account ownership. - 44e5458: Remove the legacy
composio.tools.createCustomTool(...)in-memory registry API. Use Tool Router custom tools viaexperimental_createTool,experimental_createToolkit, andcomposio.create(..., { experimental: { customTools, customToolkits } })instead.
Patch Changes
- 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
$refpointers in tool schemas the Composio API ships without a matching$defsentry. Some toolkits (e.g.GMAIL_FETCH_EMAILS) emitoutputParameterswith"$ref": "#/$defs/FetchEmailsResponse"while never declaring a top-level$defsblock. After the strict resolver shipped with the previous Mastra fix, this causedcomposio.tools.get(...)to throwJsonSchemaRefResolutionErrorupfront, making every Gmail / Slack / Google-Calendar tool unusable throughMastraProvider. 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.dereferenceJsonSchemaaccepts 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$refstill 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$refcycles. The replaced sentinel carries a defaultdescriptionhint so LLMs consuming the wrapped tool's schema get an in-band signal that the branch is opaque; a caller-provideddescriptionsibling overrides the default (Draft 2020-12 sibling-keyword merge). Safety caps (MAX_REF_CHAIN_DEPTH,MAX_NODE_DEPTH) keep throwing in both modes. NewUnresolvedRefStrategy,UnresolvedRefReason, andDereferenceJsonSchemaOptionstype exports.MastraProvider.wrapToolopts bothinputParametersandoutputParametersinto'sentinel'mode and emits onelogger.warnper(toolSlug, ref)pair via the provider-scoped dedupSet. User-controlled segments in the warning (tool.slug,toolkit.slug,ref) areJSON.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 respectsCOMPOSIO_DISABLE_TELEMETRY=true.- The
telemetryinstance from@composio/coreis now publicly re-exported alongsidelogger, so providers can emit aggregate signals without reaching into the package's internals. - Resolvable
$defs/definitionscontinue to be inlined exactly as before — no regression in the type-info preservation contract introduced by the previous Mastra fix.
1ba66ca: Fix
tools.execute(andtools.get/tools.list) failing with aZodErrorfor 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.
0.10.0
Minor Changes
- 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. ACL updates remain on the domain-specific connectedAccounts.updateAcl() mount, with experimental.updateAcl() kept as an experimental compatibility alias.
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 composio.connectedAccounts.updateAcl('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'],
});
0.9.1
Patch Changes
- 84a3a07: Add
accountTypeand per-user ACL support for SHARED connected accounts.accountTypeon create:composio.connectedAccounts.link(userId, authConfigId, { accountType: 'SHARED' })creates a SHARED connection. Default remainsPRIVATE. A SHARED connection can be used by otheruserIds, but only when the connection is explicitly pinned in a tool-router session's config and only when the requestinguserIdpasses the connection's ACL.accountTypeon retrieve:get()andlist()responses now includeaccountType('PRIVATE' | 'SHARED').aclConfigForSharedon create + retrieve: per-user ACL block —{ allowAllUsers, allowedUserIds, notAllowedUserIds }. On responses the field isundefinedwhen 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 viaPATCH. 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 raisesComposioAclOnlyForSharedError(400).ToolRouterSession.authorize()options gainaccountType+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):
1. requesting userId ∈ notAllowedUserIds → DENY
2. allowAllUsers === true → ALLOW
3. requesting userId ∈ allowedUserIds → ALLOW
4. otherwise → DENY (deny-by-default)
Limits: 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.
- Behavior change: No warning is emitted for 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.
- No public API change: initiate() returns the same ConnectionRequest shape and respects the same allowMultiple guard. ComposioLegacyConnectedAccountsEndpointRetiredError continues to surface from the 400 retired-path response.
- Test scaffolding: new mock helper 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.
0.9.0
Minor Changes
- 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.- Added:
ComposioLegacyConnectedAccountsEndpointRetiredError, exported from@composio/core. Thrown byinitiate()when the underlyingPOST /api/v3/connected_accountsreturns a 400 indicating the retiring path. Carries the migration message and apossibleFixesblock pointing atlink()and the migration guide. - Added: one-time-per-process
console.warnfrominitiate()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. - JSDoc:
initiate()now flags the retirement explicitly and points atlink()for the affected combination. Custom auth configs and non-OAuth schemes (API key, bearer, basic) are unaffected.
- Added:
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 ascreate()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, whilecomposio.use()can resume an existing session for multi-turn conversations. Sessions can preload frequently used tools, expose custom tools directly fromsession.tools(), use a direct-tools preset for agents that know their tool set upfront, and update session config mid-session withsession.update(). - 07c9bab:
connectedAccountsnow accepts bothstringandstring[]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.- Inline custom tools payload:
use()now correctly passesinlineCustomToolsPayloadandpreloadedCustomToolSlugsto the session, enabling custom tool execution and preloading on rehydrated sessions. CustomToolsMap.tools: The map now caches the rawCustomTool[]array for future inline re-injection on v3.1 search/execute requests.
Patch Changes
- c9b6525: Fix
connectedAccountsTypeScript type so a singlestringper 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
$refpointers (#/$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 AJVcan't resolve reference …error, and the resolved type information from$defssurvives the JSON-Schema → Zod → JSON-Schema round-trip instead of being silently degraded to a permissiveanyOf.- New
dereferenceJsonSchemahelper exported from@composio/coreperforms 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$refper Draft 2020-12 semantics, breaks cycles with{ type: 'object', additionalProperties: true }(matching the upstream guidance in mastra-ai/mastra#15341), and strips$defs/definitionsonce everything reachable is inlined. External (http:///https://)$refpointers are left untouched. @composio/mastracalls the helper insidewrapToolfor bothinputParametersandoutputParameters.@mastra/schema-compatdependency floor raised to^1.2.9so users automatically receive PR #15400's recursive-$refhandling.
- New
bccd32b: Expose and document the Tool Router direct-tools preset via
SessionPreset.DIRECT_TOOLS, with Python parity throughSESSION_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 normalizedLOCAL_*tool slugs exposed bysession.tools(), andcomposio.use(..., customTools/customToolkits)reuses the same custom preload preparation path as session creation.
0.8.1
Patch Changes
- 6b986cd: Bring
connectedAccounts.link()to parity withconnectedAccounts.initiate()by adding theallowMultipleoption and the matching active-connection guard. With customers being migrated offconnected_accounts/create(initiate) ontoconnected_accounts/link(SEC-339), the guard moves with them.- Added:
link(userId, authConfigId, { allowMultiple }). WhenallowMultipleisfalse(default) and the user already has anACTIVEconnection on the auth config,link()throwsComposioMultipleConnectedAccountsError— same behavior asinitiate(). Pair withaliasand a session-levelmultiAccountconfig to disambiguate at execution time. - Behavior change:
link()now performs aconnectedAccounts.list({ userIds, authConfigIds, statuses: ['ACTIVE'] })pre-flight before callingclient.link.create. Callers that intentionally create multiple connections per auth config must passallowMultiple: true.
- Added:
Python parity: same option (allow_multiple: bool = False) and same guard added to composio.connected_accounts.link().
- 1c3276b: Add
workbench.sandboxSizeto the Tool Router session config so callers can pick the workbench sandbox compute tier.- Added:
workbench.sandboxSize?: 'standard' | 'medium' | 'large' | 'xlarge'onToolRouterCreateSessionConfig. Forwarded to the API as snake_caseworkbench.sandbox_size. Optional; the server defaults it to'standard'(1 vCPU / 1 GB) when omitted, so existing callers keep current behavior. - Added:
SandboxSizeliteral union andSandboxSizeSchemazod enum, exported from@composio/coreso callers can pass tier values without stringly-typing them. - Bumped:
@composio/clientpeer to0.1.0-alpha.67to pick up the matchingsandbox_sizefield on the Tool Router session params.
- Added:
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.
0.8.0
Minor Changes
- ebc9778: Make automatic file upload/download opt-in and add scoped allowlist controls.
- Removed: the legacy
autoUploadDownloadFilesconstructor option. Code that sets it must migrate to the new opt-in flag. - Added:
dangerouslyAllowAutoUploadDownloadFiles(defaultfalse). Whentrue, the SDK collapsesfile_uploadableschemas to{ type: 'string', format: 'path' }for the model and stages local paths/URLs at execute time. - Added:
fileUploadDirs?: string[] | false— fail-closed allowlist for local upload paths.undefineddefaults to[<home>/.composio/temp];falserejects all local paths; an explicitstring[]replaces the default. - Added:
fileDownloadDir?: string— directory used to stage S3 downloads onfile_downloadableresults. - Added:
beforeFileUploadmodifier now receivessource: 'path' | 'url' | 'file'so hooks can branch on the original input type. - Added: when auto-upload is off but a tool with
file_uploadableinputs is executed, the SDK emits a one-shot warning per tool slug pointing atcomposio.files.upload()for manual staging.
- Removed: the legacy
See the changelog entry at docs/content/changelog/04-24-26-legacy-auto-upload-config-removal.mdx for migration steps.
Provider packages that depend on @composio/core are bumped to 0.8.0 alongside core in this release train so the version line stays aligned across the monorepo, even though they have no public-API changes of their own.
0.6.11
Patch Changes
- 27ed0c9: Security: Harden automatic file uploads by default-blocking local paths under common credential locations (e.g.
.ssh,.aws) and credential-like filenames (e.g..env, default SSH private key names). URLs andFileobjects are unchanged. Opt out withsensitiveFileUploadProtection: falseonly if needed; extend the denylist withfileUploadPathDenySegments.
Adds an optional beforeFileUpload hook (e.g. on composio.tools.get) to rewrite paths, return false to abort, or throw. New errors: ComposioSensitiveFilePathBlockedError, ComposioFileUploadAbortedError.
0.6.10
Patch Changes
- 670ecc9: Add missing
aliasoption toToolRouterAuthorizeFntype. TheToolRouterSession.authorize()implementation already acceptedalias, but the exported type didn't include it, causing type errors when passing{ alias: 'work-gmail' }tosession.authorize().
0.6.9
Patch Changes
- 5b5723a: release
0.6.8
Patch Changes
- 2b19ae9: Fix
customAuthParams.baseURLnot being sent to the API during tool execution. The SDK propertybaseURLis now correctly mapped to the API's expectedbase_urlfield.
0.6.7
Patch Changes
- 8dc5568: Add
workbench.enableoption to session config for disabling the workbench entirely. When set tofalse, code execution tools (COMPOSIO_REMOTE_WORKBENCH, COMPOSIO_REMOTE_BASH_TOOL) are excluded from the session. Defaults totrue.
0.6.6
Patch Changes
- e1f6516: Add custom tool support in Toolrouter
0.6.5
Patch Changes
- 476d451: Add support for files
- Add session file support
0.6.5-alpha.0
Patch Changes
- Add support for files
0.6.4
Patch Changes
- e3f1f6c: Remove telemetry payload
0.6.3
Patch Changes
- 087385d: Remove important tag auto apply when limit is set
0.6.2
Patch Changes
- Updated dependencies [eec8fd9]
- @composio/json-schema-to-zod@0.1.20
0.6.1
Patch Changes
- e746383: Fix issues with file upload corruption
0.6.0
Minor Changes
- BREAKING: Webhook verification now async with new signature
composio.triggers.verifyWebhook()now requiresawait- New required parameters:
id(webhook-id header) andtimestamp(webhook-timestamp header) - Uses Web Crypto API for Cloudflare Workers compatibility
- Supports v1, v2, and v3 webhook formats
BREAKING: Mastra provider updated to v1 API
- Requires Mastra v1 and Node.js v22.13.0+
- New initialization pattern with Mastra instance
- E2E tests for Zod v3 and v4 compatibility
Platform-specific optimizations
- Separate file tool modifiers for Node.js and Cloudflare Workers
- Platform-specific config defaults (autoUploadDownloadFiles)
- Removed node:buffer usage, replaced with Uint8Array
- Removed node:crypto from triggers for edge runtime support
Bug fixes
- Fixed tool fetching with specific version constraints
- Improved type safety across the SDK
0.5.5
Patch Changes
- b132aad: Update client dependencies and introduce experimentatl tool router features
0.5.4
Patch Changes
- b3f5875: Fix multi connected account flag to check only active accounts
0.5.3
Patch Changes
- 498505d: Fix file upload and download in tools with anyOf schemas
0.5.2
Patch Changes
- 277f02b: Fix bundling issues with external providers
0.5.1
Patch Changes
- 3055048: Update client dependencies and auth config update params to be optional
0.5.0
Minor Changes
- ded64be: Add Cloudflare Workers compatibility for
@composio/core, tested end-to-end.
0.4.0
Minor Changes
- c7e1217: Add support for dedicated tools for tool router
0.3.4
Patch Changes
- 019f54f: Fix method binding for top level tool router methods
0.3.3
Patch Changes
- a76b002: Add support for enable/disable tags and search toolkits in tool router
0.3.2
Patch Changes
- 69cfede: Update client version and add openWorldHintSupport in toolrouter tag filters. Removes isLocal param in toolkit fetching
0.3.1
Patch Changes
- 73db5f5: Fix callback url not working in toolrouter's session.authorize()
0.3.0
Minor Changes
- 07551cd: Add support for native tool execution in tool router
- 9e002c5: Minor fixes
- f0e67c4: Update API client and tool router types
- 31521bd: Update typedocs and examples for toolkit versions
- 9e002c5: Alpha release of tool router
0.2.7-alpha.4
Patch Changes
- 07551cd: Add support for native tool execution in tool router
0.2.7-alpha.3
Patch Changes
- f0e67c4: Update API client and tool router types
0.2.7-alpha.2
Patch Changes
- 31521bd: Update typedocs and examples for toolkit versions
0.2.7-alpha.1
Patch Changes
- Minor fixes
0.2.7-alpha.0
Patch Changes
- Alpha release of tool router
0.2.6
Patch Changes
- b5cc23f: Fix dangerously skip version check in non agentic providers, Throw error instead of process.exit when api key doesn't exist, bump zod-to-json-schema to 3.25.0, which supports "zod/3"
- Updated dependencies [b5cc23f]
- @composio/json-schema-to-zod@0.1.19
0.2.5
Patch Changes
- e2762f2: Fix non-agentic providers to work without specifying versions
0.2.4
Patch Changes
- 97c4138: Update composio client version and add support for toolkit version in fetching trigger types
0.2.3
Patch Changes
- f88ab99: Fix: SDK telemetry methods and request headers
0.2.2
Patch Changes
- cfc2c50: Update zod version to 4
- Updated dependencies [cfc2c50]
- @composio/json-schema-to-zod@0.1.18
0.2.1
Patch Changes
- 6135896: Add toolkit versions support and deprecation flags to TypeScript SDK
This PR adds support for toolkit versions in the TypeScript SDK and introduces new fields for tracking tool deprecation status and no-auth capabilities.
### Core Features
- Toolkit Versions Support:
- Added toolkit_versions parameter to the Triggers class, defaulting to "latest"
- Made Triggers class generic to accept provider configuration
- Pass toolkit_versions when listing trigger types
### New Fields
- Tool Types:
- Added isDeprecated field to track deprecated tools
- Added isNoAuth field to identify tools that support no-auth mode
- Trigger Types:
- Added version field to track trigger versions
- Toolkit Metadata:
- Added availableVersions array to track all available versions
### Code Changes
- Updated Composio class to pass config to Triggers constructor
- Updated Tools.get() to include new isDeprecated and isNoAuth fields
- Updated transformers for toolkits and triggers to handle new fields
- Added TypeScript types for all new fields
### Tests
- Updated trigger tests to account for toolkit_versions and cursor parameters
- Fixed generic type usage in Triggers test declarations
- All 376 tests passing ✅
### Dependencies
- Updated @composio/client to version 0.1.0-alpha.38
- Updated pnpm-lock.yaml with dependency resolution changes
## Testing
pnpm --filter @composio/core test
All tests passing (376/376) ✅
## Breaking Changes
None - All changes are backwards compatible with default values
## Related Issues
Fixes toolkit version handling and deprecation flag tracking in TypeScript SDK
0.2.0
Minor Changes
- 157bf7b: ### Added
- Version validation for manual tool execution: Tools now require explicit toolkit version specification when executing manually to prevent unexpected behavior from
latestversion changes - New
dangerously_skip_version_checkparameter (Python) /dangerouslySkipVersionCheck(TypeScript): Optional flag to bypass version validation (use with caution) ToolVersionRequiredErrorexception (Python): Raised when attempting to execute tools withlatestversion without skip flag, includes helpful error messages with 4 possible fixesComposioToolVersionRequiredErrorerror (TypeScript): Parallel implementation for TypeScript SDK with detailed error context and resolution suggestions- Comprehensive test coverage: Added 19 new test methods in Python covering all tool execution scenarios including version resolution, error handling, modifiers, and environment variables
- Version validation for manual tool execution: Tools now require explicit toolkit version specification when executing manually to prevent unexpected behavior from
### Changed
- Tool execution behavior: Manual execution via tools.execute() now validates toolkit versions before API calls
- Agentic provider flows: Automatically set dangerously_skip_version_check=True internally to maintain backward compatibility for framework integrations
- Instance-level version resolution: Both execute() and _execute_tool() methods now consistently resolve versions from instance-level toolkit_versions configuration
- Modifier support: Added dangerously_skip_version_check to modifier parameter types for complete flow coverage
- Test version format: Updated all test files to use production date-based version format (20251201_XX) instead of semantic versioning
### Fixed
- Consistent version handling: Removed toolkit_versions parameter from _execute_tool() in favor of instance-level configuration, ensuring consistent version resolution across the SDK
- Code formatting: Applied ruff formatting to all modified Python files
- Array parsing to ZodSchema: Fixes in json-schema-to-zod to parse array without properties and with properties
### Migration Guide
When manually executing tools, you must now specify toolkit versions:
Option 1: Pass explicit version parameter
tools.execute("GITHUB_CREATE_ISSUE",
arguments={...},
version="20251201_01"
)
Option 2: Configure at SDK initialization
tools = Tools(client, provider,
toolkit_versions={"github": "20251201_01"}
)
Option 3: Use environment variables
export COMPOSIO_TOOLKIT_VERSION_GITHUB=20251201_01
Option 4: Skip validation (not recommended)
tools.execute("GITHUB_CREATE_ISSUE",
arguments={...},
dangerously_skip_version_check=True
)
### Developer Notes
- Agentic framework integrations (LangChain, CrewAI, etc.) are not affected as they automatically use the skip flag
- The latest version can still be used with the skip flag, but specific versions are strongly recommended
- Error messages include all available resolution options for better developer experience
Patch Changes
- Updated dependencies [157bf7b]
- @composio/json-schema-to-zod@0.1.17
0.1.55
Patch Changes
- 8741165: Add zod 4 support via zod/v3 and fix zod schema parsing
- Updated dependencies [8741165]
- @composio/json-schema-to-zod@0.1.16
0.1.54
Patch Changes
- e5b9db3: Fix exports for experimental tool router
0.1.53
Patch Changes
- 9a1b0e9: - Adds the new experiemntal ToolRouter, Deprecates the existing MCP experience and adds the new MCP components.
- The old MCP components can be accessed via
deprecated.mcpuntil the next release, where it will get removed. - Fixes
toolkits.listandtoolkits.getmethods to adddescriptionto connection fields
- The old MCP components can be accessed via
0.1.52
Patch Changes
- 7077cee: Add tool versioning support
0.1.51
Patch Changes
- b9b005a: Add support for composio connect links
0.1.50
Patch Changes
- Updated dependencies [51033d8]
- @composio/json-schema-to-zod@0.1.15
0.1.49
Patch Changes
- 5027e18: Fix openai responses schema parsing
- Updated dependencies [5027e18]
- @composio/json-schema-to-zod@0.1.14
0.1.48
Patch Changes
- bb32cc2: Bump openai responses and deprecate openai assistant
0.1.47
Patch Changes
- 05ce9c6: Fix make access token and token type optional in oauth scheme
0.1.46
Patch Changes
- ee12d25: Fix long filenames while uploading files from URL
- 9458513: Feat: Add flags to disable version check
0.1.45
Patch Changes
- Updated dependencies
- @composio/json-schema-to-zod@0.1.13
0.1.44
Patch Changes
- b4b8b94: Fix telemetry flags and disable when passed
0.1.43
Patch Changes
- eb7691e: Add strict mode to vercel provider
0.1.42
Patch Changes
- Updated dependencies
- @composio/json-schema-to-zod@0.1.12
0.1.41
Patch Changes
- 025600f: Bump composio client version to 0.1.0-alpha.31
0.1.40
Patch Changes
- 1664c34: Fix auth config creation/updation methods to accept tool access configs
0.1.39
Patch Changes
- Fix jsonSchema to zod parsing which used to eliminate min/max and examples proeperties
- Updated dependencies
- @composio/json-schema-to-zod@0.1.11
0.1.38
Patch Changes
- 6c980ad: Add generics for CLI trigger type generation
0.1.37
Patch Changes
- 09c4a26: Fix issues with tools.execute requiring userId for no auth apps
0.1.36
Patch Changes
- 7276d1e: Fix issues with json schema to zod parsing causing nested objects to be marked as required
- c223e54: Fix file upload handlers
- 7276d1e: Fix issues with objects with default values being marked as required
- 9a10986: Fix: Relax strict type/schema validations on API responses
- 06612f5: Downgrade chalk to v4 to allow CJS as well
- cb1b401: Update composio api client to latest version
- da57771: dont't validate if authConfigIds is provided
- 91c3647: Update deps
- b001330: Fix package bumps
- 77e96e4: Fix JSON Schema to Zod Parsing
- ea79c18: Bump packages
- cb1b401: Bump packages for authconfig fixes
- ea79c18: Update packages
- a79dfac: Relax connected account schema parsing
- Create stable release
- ea79c18: Fix: Gracefully handle connected account responses for missing fields
- 91c3647: Fix proxy execute params and bump langchain packages
- ea79c18: Bump packages
- Updated dependencies [7276d1e]
- Updated dependencies [7276d1e]
- Updated dependencies [06612f5]
- Updated dependencies [77e96e4]
- Updated dependencies [cb1b401]
- Updated dependencies
- @composio/json-schema-to-zod@0.1.10
0.1.36-next.13
Patch Changes
- 77e96e4: Fix JSON Schema to Zod Parsing
- Updated dependencies [77e96e4]
- @composio/json-schema-to-zod@0.1.10-next.5
0.1.36-next.12
Patch Changes
- Update deps
0.1.36-next.11
Patch Changes
- Fix proxy execute params and bump langchain packages
0.1.36-next.10
Patch Changes
- Fix: Relax strict type/schema validations on API responses
0.1.36-next.9
Patch Changes
- 9fa49ec: Update composio api client to latest version
- Bump packages for authconfig fixes
- Updated dependencies
- @composio/json-schema-to-zod@0.1.10-next.4
0.1.36-next.8
Patch Changes
- Fix package bumps
0.1.36-next.7
Patch Changes
- da57771: dont't validate if authConfigIds is provided
0.1.36-next.6
Patch Changes
- 06612f5: Downgrade chalk to v4 to allow CJS as well
- Relax connected account schema parsing
- Updated dependencies [06612f5]
- @composio/json-schema-to-zod@0.1.10-next.3
0.1.36-next.5
Patch Changes
- dd630fe: Bump packages
- Bump packages
0.1.36-next.4
Patch Changes
- Update packages
0.1.36-next.3
Patch Changes
- Fix: Gracefully handle connected account responses for missing fields
0.1.36-next.2
Patch Changes
- Fix issues with objects with default values being marked as required
- Updated dependencies
- @composio/json-schema-to-zod@0.1.10-next.1
0.1.36-next.1
Patch Changes
- Fix issues with json schema to zod parsing causing nested objects to be marked as required
- Updated dependencies
- @composio/json-schema-to-zod@0.1.10-next.0
0.1.36-next.0
Patch Changes
- Fix file upload handlers
0.1.35
Patch Changes
- git status
0.1.34
Patch Changes
- Add exports for connection request
0.1.33
Patch Changes
- Fix types and exports
0.1.32
Patch Changes
- Add support for File type in uploading files
0.1.31
Patch Changes
- e660385: Fix file upload / download
0.1.30
Patch Changes
- Improved support for file handling
0.1.29
Patch Changes
- Add file upload / download modifiers
0.1.28
Patch Changes
- Add MCP support for providers
0.1.27
Patch Changes
- Remove cusrsor and important flags from tools.get
0.1.26
Patch Changes
- Fix function signatures for toolkits auth fields
0.1.25
Patch Changes
- Add MCP server to composio SDk
0.1.24
Patch Changes
- Fix auth schemes for creating connected accounts
0.1.23
Patch Changes
- Improvements in DX in triggers and bug fixes in tools
0.1.22
Patch Changes
- Adds support for connected accounts allowMultiple flag, and other improvements
0.1.21
Patch Changes
- Add host name support in SDK
- Updated dependencies
- @composio/json-schema-to-zod@0.1.9
0.1.20
Patch Changes
- 1ab34ef: Fix json schema support in tools
- Updated dependencies [1ab34ef]
- @composio/json-schema-to-zod@0.1.8
0.1.19
Patch Changes
- c8e89d5: Fix telemetry transport
- Updated dependencies [c8e89d5]
- @composio/json-schema-to-zod@0.1.7
0.1.18
Patch Changes
- 37a1f01: Feat better connected account creation flow
- Updated dependencies [37a1f01]
- @composio/json-schema-to-zod@0.1.6
0.1.17
Patch Changes
- df31cc2: Fix json schema parsing
- Updated dependencies [df31cc2]
- @composio/json-schema-to-zod@0.1.5
0.1.16
Patch Changes
- f943ba4: Export all the types from the core SDK
- Updated dependencies [f943ba4]
- @composio/json-schema-to-zod@0.1.2
0.1.15
Patch Changes
- 208e320: Update json schema transformations issues related to strict mode
- Updated dependencies [208e320]
- @composio/json-schema-to-zod@0.1.2
0.1.14
Patch Changes
- 4ddfafc: Add json schema to zod schema
- Updated dependencies [4ddfafc]
- @composio/json-schema-to-zod@0.1.1
0.1.13
Patch Changes
- 040b5a4: Ability to create sessions for transferring request ids
0.1.12
Patch Changes
- c1443db: Improved error handling and telemetry
- b121e73: Update packages to stable version
- f144202: Update tsdocs across all the functions
- ba8d991: Fix initiate connection flows and api issues
- ca59bcd: Update documentations and fix API discrepencies
- e51680c: Fix versioning with changesets
- 0b15376: Add custom toolkit examples
- de3f522: Stable version with test coverage and other stuff
- a2f9537: Update tools.get to accept discriminated unions
- 83a0d15: Test github ci publish
- eeec413: Rename modifiers, add docs and other miscellanious improvements
0.1.12-alpha.16
Patch Changes
- 0b15376: Add custom toolkit examples
0.1.12-alpha.15
Patch Changes
- f144202: Update tsdocs across all the functions
0.1.12-alpha.14
Patch Changes
- 83a0d15: Test github ci publish
0.1.12-alpha.13
Patch Changes
- a2f9537: Update tools.get to accept discriminated unions
0.1.12-alpha.12
Patch Changes
- de3f522: Stable version with test coverage and other stuff
0.1.12-alpha.11
Patch Changes
- Improved error handling and telemetry
0.1.12-alpha.10
Patch Changes
- eeec413: Rename modifiers, add docs and other miscellanious improvements
0.1.12-alpha.9
Patch Changes
- ba8d991: Fix initiate connection flows and api issues
0.1.12-alpha.8
Patch Changes
- ca59bcd: Update documentations and fix API discrepencies
0.1.12-alpha.7
Patch Changes
- e51680c: Fix versioning with changesets
0.1.0
Patch Changes
- Initial release