Skip to content

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: address review feedback on sandbox-size + link allow_multiple PR

Zen Agent189cd0c7cdad
diff --git a/docs/content/changelog/04-28-26-sdk-link-allow-multiple.mdx b/docs/content/changelog/04-28-26-sdk-link-allow-multiple.mdx
index bb30925ef..d1e0aff5d 100644
--- a/docs/content/changelog/04-28-26-sdk-link-allow-multiple.mdx
+++ b/docs/content/changelog/04-28-26-sdk-link-allow-multiple.mdx
@@ -9,7 +9,7 @@ date: '2026-04-28'
<Callout type="warn">
**Behavior change**
-Before: `link()` would happily create a second `ACTIVE` connection for the same `(user_id, auth_config_id)` pair without a follow-up patch.
+Before: `link()` would happily create a second `ACTIVE` connection for the same `(user_id, auth_config_id)` pair without checking for an existing `ACTIVE` connection first.
After: `link()` first calls `connectedAccounts.list({ userIds, authConfigIds, statuses: ['ACTIVE'] })`. If any active connection exists, `link()` throws `ComposioMultipleConnectedAccountsError` unless the caller passes `allowMultiple: true` (TypeScript) / `allow_multiple=True` (Python).
</Callout>
diff --git a/docs/content/changelog/04-28-26-sdk-sandbox-size.mdx b/docs/content/changelog/04-28-26-sdk-sandbox-size.mdx
index cbd9aecd9..94408c047 100644
--- a/docs/content/changelog/04-28-26-sdk-sandbox-size.mdx
+++ b/docs/content/changelog/04-28-26-sdk-sandbox-size.mdx
@@ -26,8 +26,6 @@ The field is optional and defaults to `standard` server-side when omitted, so ex
| TypeScript `@composio/core` | v0.8.0 | **v0.8.1** |
| Python `composio` | v0.12.0 | **v0.12.1** |
-Stainless clients are bumped in the same release: `@composio/client` to `0.1.0-alpha.67` and `composio-client` to `1.34.0`.
-
### Usage
**TypeScript** (camelCase on the SDK surface):
@@ -59,8 +57,8 @@ session = composio.create(
The `SandboxSize` literal alias is available at `composio.core.models.tool_router.SandboxSize`.
-### Behavior on patch
+### Updating an existing session
-Changing `sandbox_size` on an existing session recreates the sandbox on next access. The sandbox's in-memory filesystem state is lost, but the persistent `/mnt/files/` mount survives the restart.
+Calling `session.update()` (or the equivalent `PATCH /api/v3/tool_router/sessions/{id}`) with a different `sandbox_size` recreates the sandbox on next access. The sandbox's in-memory filesystem state is lost, but the persistent `/mnt/files/` mount survives the restart.
See [Configuring Sessions → Sandbox compute tier](/docs/configuring-sessions#sandbox-compute-tier) for the full reference.
diff --git a/docs/content/docs/configuring-sessions.mdx b/docs/content/docs/configuring-sessions.mdx
index b59cd038e..736d3ea42 100644
--- a/docs/content/docs/configuring-sessions.mdx
+++ b/docs/content/docs/configuring-sessions.mdx
@@ -209,6 +209,11 @@ When disabled:
The workbench runs in a per-session sandbox. You can pick a compute tier to match the workload — heavier code execution or larger in-memory data benefits from a bigger sandbox. The tier is passed via `workbench.sandbox_size` (snake_case on the wire; `sandboxSize` in the TypeScript SDK).
+<Callout type="info">
+Requires `@composio/core` ≥ `0.8.1` (TypeScript) or `composio` ≥ `0.12.1` (Python). Older SDKs reject `sandboxSize` (TypeScript) or silently drop `sandbox_size` (Python). See the [release notes](/docs/changelog/2026/04/28).
+</Callout>
+
+
| Tier | vCPU | RAM |
| ---------- | ---- | ----- |
| `standard` | 1 | 1 GB |
diff --git a/docs/content/docs/workbench.mdx b/docs/content/docs/workbench.mdx
index 6d90d7903..d3bfb000f 100644
--- a/docs/content/docs/workbench.mdx
+++ b/docs/content/docs/workbench.mdx
@@ -57,7 +57,7 @@ The sandbox runs as a persistent Jupyter notebook. Variables, imports, files, an
### Compute tier
-Sandboxes default to `standard` (1 vCPU / 1 GB RAM). For heavier workloads — large dataframes, ML preprocessing, big bulk operations — pick a larger tier when creating the session via `workbench.sandboxSize` (TypeScript) / `workbench.sandbox_size` (Python). Available tiers: `standard`, `medium` (2 vCPU / 2 GB), `large` (4 vCPU / 4 GB), `xlarge` (8 vCPU / 8 GB). See [Configuring Sessions → Sandbox compute tier](/docs/configuring-sessions#sandbox-compute-tier) for examples.
+Sandboxes default to `standard` (1 vCPU / 1 GB RAM). For heavier workloads — large dataframes, ML preprocessing, big bulk operations — pick a larger tier when creating the session via `workbench.sandboxSize` (TypeScript) / `workbench.sandbox_size` (Python). Available tiers: `standard`, `medium` (2 vCPU / 2 GB), `large` (4 vCPU / 4 GB), `xlarge` (8 vCPU / 8 GB). Requires `@composio/core` ≥ `0.8.1` or `composio` ≥ `0.12.1`. See [Configuring Sessions → Sandbox compute tier](/docs/configuring-sessions#sandbox-compute-tier) for examples.
<Callout type="info">
**Pricing:** Sandboxes are not billed today. Composio plans to begin billing for sandbox usage soon (metered by tier and runtime).