- Add ComposioToolInputRequiredError, thrown when a session tool call returns result_type input_required, carrying inputRequests and a non-enumerable requestState
- Add resultType to session execute responses, always present, and read it rather than error to determine success or failure
- Add userId to tools.proxyExecute(), sent as user_id for 2FA-enabled connected account checks
- Update the owned API client to @composio/client@2.0.0-rc.11
- Session tool calls that need user input throw ComposioToolInputRequiredError instead of returning a failed result, and local custom tools let this error propagate
- Provider-wrapped session tools, provider tool calls bound to a session, and merged COMPOSIO_MULTI_EXECUTE_TOOL results derive successful from resultType alone behavior changed · inferred, marked in the notes below
- Session execute answers without a result_type, or with an unknown value, throw ValidationError
- A COMPOSIO_MULTI_EXECUTE_TOOL batch mixing local and remote tools throws ComposioToolInputRequiredError when the remote half needs user input
- ToolRouterSessionConfig and ToolRouterSessionConfigHistoryConfig are now the client's own config types, with instant always present signature changed · inferred, marked in the notes below
- Session config is returned as the API sent it, with no runtime validation of instant and no removal of premium_usage behavior changed · inferred, marked in the notes below
- ToolRouterSessionExecuteResponse requires resultType, so custom ToolCallSession implementations must return it from execute() signature changed · inferred, marked in the notes below
- Update the owned API client to @composio/client@2.0.0-rc.9
- Send product identity, product version, language, and runtime version with API requests, identifying core and slim packages separately
- Session tool executions and proxied calls no longer retry after timeouts, connection errors, or 408/409/429/5xx responses
- Default RemoteFile.save() creates files exclusively and adds a copy number on collision so repeated saves return distinct paths behavior changed · inferred, marked in the notes below
- A patternProperties key requiring lookaround or a backreference now fails conversion with InvalidPatternError (reason unsupported) behavior changed · inferred, marked in the notes below
- Tool schemas using anyOf, oneOf, allOf, $ref, or similar keywords are no longer rejected by OpenAI and Anthropic, and top-level type object is restored for provider tool parameters
- Tool patterns with escapes such as \_ or \: no longer cause every call to the tool to fail
- RemoteFile.save() without a path accepts file names with Windows-reserved characters by replacing them with underscores
- RemoteFile.save() truncates names longer than 128 bytes while keeping the extension, and prefixes reserved device names such as NUL with an underscore
- Tool schema patterns match astral characters such as emoji as single characters, per JSON Schema's Unicode regex dialect
- Removed the unused ToolRouterInstantResponseSchema and ToolRouterInstantResponse exports inferred, marked in the notes below
- Tool schema pattern and patternProperties regexes run on a linear-time engine (RE2 via re2js), preventing catastrophic backtracking from hanging argument validation
9 changes to check, marked in the notes below
From Composio
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 theexecute/proxyExecutehelpers passed to custom tools throw the newComposioToolInputRequiredErrorin 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 oninputRequestsand the opaquerequest_stateonrequestState.requestStateis continuation state, so it is a non-enumerable property: read it aserror.requestState, andconsole.error(error),util.inspect(error)andJSON.stringify(error)leave it out. Nothing was executed and the call is not retried. The SDK does not submit answers yet. behavior changed · inferredEvery session tool that ran reports
result_typeascompletedorfailed, and a failed execution can carry anullor emptyerror.session.execute()and the custom toolexecutehelper return it as the newresultType, which is always present; read it rather thanerrorto tell a failure from a success. Provider-wrapped session tools, provider tool calls bound to a session, and the mergedCOMPOSIO_MULTI_EXECUTE_TOOLresult setsuccessfulfrom it alone, so a failure without error text is no longer reported as successful.erroris returned as the API sent it. A session execute answer withoutresult_type, or with a value this SDK does not know, throwsValidationErrorinstead of being read as a success or a failure.A
COMPOSIO_MULTI_EXECUTE_TOOLbatch that mixes local custom tools with remote tools now throwsComposioToolInputRequiredErrorwhen 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, withoutinputRequestsorrequestState. 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. signature changed · inferred- 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. behavior changed · inferred ToolRouterSessionExecuteResponserequiresresultType. A customToolCallSessionpassed to a provider must return it fromexecute(), becausesuccessfulis no longer derived fromerror. signature changed · inferred- Removed the unused
ToolRouterInstantResponseSchemaandToolRouterInstantResponseexports. UseToolRouterSessionConfig['instant']for the Instant policy the API returns. removed · inferred
-
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.
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(). behavior changed · inferred - 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. behavior changed · inferred - 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. behavior changed · inferred - 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. behavior changed · inferred - Updated dependencies [077ceb3]
- Updated dependencies [d9f6291]
- @composio/json-schema-to-zod@0.3.4