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: fix requireExplicitSelection description in multi-account docs
The previous description incorrectly said the agent must use connectedAccounts pinning. The actual behavior is that when enabled and a toolkit has multiple active connected accounts, the agent must provide the `account` parameter in the tool execution call. When disabled, the most recently connected active account is used automatically. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> Co-authored-by: abir <abir@composio.dev>
Zen Agent committed
Apr 15, 2026 at 01:02 UTC
64c6a54518c1f38d944d8bc8c44b2dfaf036d9ab
1 file changed
+1
-1
docs/content/docs/managing-multiple-connected-accounts.mdx
+1
-1
@@ -45,7 +45,7 @@ const session = await composio.create("user_123", {
45
|--------|------|---------|-------------|
46
| `enable` | `boolean` | `false` | Enable multi-account mode for this session |
47
| `maxAccountsPerToolkit` / `max_accounts_per_toolkit` | `number` | `5` | Maximum connected accounts per toolkit (2-10) |
48
-| `requireExplicitSelection` / `require_explicit_selection` | `boolean` | `false` | When true, the agent must specify which account to use via [`connectedAccounts` pinning](#selecting-a-specific-account-for-a-session) instead of defaulting to the most recent |
48
+| `requireExplicitSelection` / `require_explicit_selection` | `boolean` | `false` | When true and a toolkit has multiple active connected accounts, the agent must provide the `account` parameter in the tool execution call to select which account to use. When false, the default account (most recently connected active account) is used automatically |
49
50
When multi-account mode is disabled (the default), each session uses the most recently connected account for each toolkit.
51