@devries-cameron20 / composio Mirror · read-only / commits / 189cd0c7c
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.

Mirrored from https://github.com/Camo67/composio.git

Synced Nov 21, 22:15 UTC

docs: address review feedback on sandbox-size + link allow_multiple PR

- changelog/sdk-sandbox-size: drop the stainless-client bump line — internal implementation detail, not user-facing (dhawal1). - changelog/sdk-sandbox-size: rename ambiguous "Behavior on patch" section header to "Updating an existing session" and clarify it's about `session.update()` / PATCH semantics, not the npm patch release (dhawal1: "is patch live?"). - changelog/sdk-link-allow-multiple: rephrase the "before" line so the before/after distinction is unambiguous — `link()` previously didn't check for an existing ACTIVE connection, full stop (Copilot). - configuring-sessions: add an SDK-version Callout under the Sandbox compute tier heading so a reader landing directly on this page knows which @composio/core / composio versions are required and what older SDKs do (Copilot). - workbench: same SDK-version note inline in the Compute tier paragraph (Copilot). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

Zen Agent committed Apr 28, 2026 at 13:12 UTC 189cd0c7cdad01cce1a483b856a06b914c4dbff1
4 files changed +9 -6
docs/content/changelog/04-28-26-sdk-link-allow-multiple.mdx
+1 -1
@@ -9,7 +9,7 @@ date: '2026-04-28'
9 <Callout type="warn">
10 **Behavior change**
11
12 -Before: `link()` would happily create a second `ACTIVE` connection for the same `(user_id, auth_config_id)` pair without a follow-up patch.
12 +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.
13
14 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).
15 </Callout>
docs/content/changelog/04-28-26-sdk-sandbox-size.mdx
+2 -4
@@ -26,8 +26,6 @@ The field is optional and defaults to `standard` server-side when omitted, so ex
26 | TypeScript `@composio/core` | v0.8.0 | **v0.8.1** |
27 | Python `composio` | v0.12.0 | **v0.12.1** |
28
29 -Stainless clients are bumped in the same release: `@composio/client` to `0.1.0-alpha.67` and `composio-client` to `1.34.0`.
30 -
29 ### Usage
30
31 **TypeScript** (camelCase on the SDK surface):
@@ -59,8 +57,8 @@ session = composio.create(
57
58 The `SandboxSize` literal alias is available at `composio.core.models.tool_router.SandboxSize`.
59
62 -### Behavior on patch
60 +### Updating an existing session
61
64 -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.
62 +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.
63
64 See [Configuring Sessions → Sandbox compute tier](/docs/configuring-sessions#sandbox-compute-tier) for the full reference.
docs/content/docs/configuring-sessions.mdx
+5
@@ -209,6 +209,11 @@ When disabled:
209
210 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).
211
212 +<Callout type="info">
213 +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).
214 +</Callout>
215 +
216 +
217 | Tier | vCPU | RAM |
218 | ---------- | ---- | ----- |
219 | `standard` | 1 | 1 GB |
docs/content/docs/workbench.mdx
+1 -1
@@ -57,7 +57,7 @@ The sandbox runs as a persistent Jupyter notebook. Variables, imports, files, an
57
58 ### Compute tier
59
60 -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.
60 +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.
61
62 <Callout type="info">
63 **Pricing:** Sandboxes are not billed today. Composio plans to begin billing for sandbox usage soon (metered by tier and runtime).