@devries-cameron20 / composio-1 / commits / 89c46b1d9
Fork 0

Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.

docs: update documentation for new changelog entries (#4917)

## Summary Automated documentation updates triggered by new changelog entries merged to next. Generated by Codex via GitHub Actions. Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>

sdkrelease[bot] committed Oct 22, 2026 at 18:09 UTC 89c46b1d95d42912a884ef3dca172ceea1e13ce8
2 files changed +31
docs/content/docs/configuring-sessions.mdx
+22
@@ -26,6 +26,10 @@ By default, a session has access to every toolkit in the Composio catalog. Your
26
27 You can also attach local custom tools and custom toolkits that run in-process alongside Composio tools. See [Custom tools and toolkits](/docs/extending-sessions/custom-tools-and-toolkits).
28
29 +<Callout type="warn">
30 +Both SDKs pass product and runtime identity through the API client's `identity` option. If you configure custom default or request headers, remove identity headers such as `x-source`, `x-framework`, `x-sdk-version`, and `x-client-*`. The client rejects attempts to override them.
31 +</Callout>
32 +
33 ### API key permissions
34
35 If you use a [scoped project API key](/reference/authenticating-to-composio/project-api-key-permissions), grant permissions for the session operations your application needs:
@@ -53,6 +57,22 @@ In Python, `session.config.instant` is a model when it contains a policy. Read i
57 If you implement the TypeScript `Session` interface yourself, include the required `config` member. Sessions created by the SDK provide it automatically.
58 </Callout>
59
60 +## Requiring tool approval
61 +
62 +Require approval before selected session tools run by adding `requireApproval` (`require_approval` in Python) to toolkit, tool, or tag filters. These approval settings are experimental.
63 +
64 +| Scope | TypeScript session option | Python session option |
65 +| --- | --- | --- |
66 +| All tools in a toolkit | `toolkits: { requireApproval: ["gmail"] }` | `toolkits={"require_approval": ["gmail"]}` |
67 +| Specific tools in a toolkit | `tools: { gmail: { requireApproval: ["GMAIL_SEND_EMAIL"] } }` | `tools={"gmail": {"require_approval": ["GMAIL_SEND_EMAIL"]}}` |
68 +| Tools with matching tags | `tags: { requireApproval: ["destructiveHint"] }` | `tags={"require_approval": ["destructiveHint"]}` |
69 +
70 +You can combine an approval list with `enable` or `disable` in the same filter object. An approval list alone does not restrict which tools are available.
71 +
72 +When execution needs approval, catch `ComposioToolInputRequiredError` from `@composio/core` in TypeScript or `ToolInputRequiredError` from `composio.exceptions` in Python. Display `inputRequests` (`input_requests`) and wait for the person's answers. Repeat the same tool or meta-tool call with `inputResponses` and `requestState` (`input_responses` and `request_state`), preserving the state from the error. Forward decline and cancel answers unchanged. See [handling input requests](/docs/how-composio-works#handling-requests-for-user-input) for the continuation flow.
73 +
74 +For MCP clients, configure the [approval fallback](/docs/sessions-via-mcp#approval-without-elicitation-support) if the client cannot ask for approval.
75 +
76 ## Enabling toolkits
77
78 To limit a session to specific toolkits, pass an array of toolkit slugs. The agent can only discover and use tools from these toolkits.
@@ -1056,6 +1076,8 @@ console.log(result.data, result.resultType);
1076
1077 The exported `ToolRouterSessionMetaToolSlug` type lists the accepted slugs. The response includes `resultType` (`result_type` in Python). If execution needs input, such as approval, the SDK raises `ComposioToolInputRequiredError` (`ToolInputRequiredError` in Python). Calls are sent once without retries, so retry only when the operation is safe to repeat.
1078
1079 +In TypeScript, the third argument holds input-response options: `session.executeMeta(slug, args, { inputResponses, requestState })`. Request options belong in the fourth argument. To pass only request options, use `session.executeMeta(slug, args, undefined, requestOptions)`.
1080 +
1081 `COMPOSIO_MULTI_EXECUTE_TOOL` calls through this method run on the backend. Custom tools named in those calls are not executed in your process.
1082
1083 ### authorize()
docs/content/docs/sessions-via-mcp.mdx
+9
@@ -58,6 +58,15 @@ Resuming a stored session? Pass the same flag, `composio.use(sessionId, { mcp: t
58 The MCP endpoint and `session.tools()` are backed by the same session. Toolkits, auth configs, and connected accounts you set when [configuring the session](/docs/configuring-sessions) apply to both.
59 </Callout>
60
61 +## Approval without elicitation support
62 +
63 +You can [require approval for session tools](/docs/configuring-sessions#requiring-tool-approval). If your MCP client cannot ask for approval through elicitation, set `experimental.noElicitationSupportFallback` in TypeScript or `experimental.no_elicitation_support_fallback` in Python when creating the session:
64 +
65 +- `"deny"` blocks the call when the client cannot ask for approval.
66 +- `"allow"` lets the call run without asking for approval.
67 +
68 +For example, pass `experimental: { noElicitationSupportFallback: "deny" }` in TypeScript or `experimental={"no_elicitation_support_fallback": "deny"}` in Python alongside `mcp: true` or `mcp=True`.
69 +
70 ## What the MCP headers carry
71
72 `session.mcp.headers` holds the credential the SDK used to create or load the session, and nothing else. No other default header and no ambient `COMPOSIO_API_KEY` is copied in.