@devries-cameron20 / composio Mirror · read-only / commits / 8dcc9b991
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, 17:15 UTC

docs(sandbox): clarify Composio doesn't run/replace your agent (LLM tokens are sandbox-only & optional) (#3933)

# Description Customers evaluating Composio see references to **LLM tokens** and assume Composio is handing them an agent/LLM that *replaces* their own — i.e. that they'd be swapping their agent for ours. It isn't: Composio discovers, authenticates, and executes tools; it never proxies the customer's model or runs an agent on their behalf. The one place Composio itself calls a model is **inside the sandbox** (the optional `invoke_llm` helper + AI-assisted conveniences like error correction). The sandbox is opt-in per session (`sandbox: { enable: true }`), so this LLM usage is entirely optional and can be disabled. This PR adds a short callout to the **Remote sandbox** docs page (`docs/content/docs/sandbox/remote.mdx`) that says exactly that — placed right where `invoke_llm` and the sandbox are introduced, with anchor links to the `invoke_llm` helper, error correction, and session configuration. It kills the "are they replacing my agent?" misconception at its source. The copy is deliberately accurate to today's state: it does **not** claim we bill LLM tokens (sandbox billing is still upcoming and the public pricing page only lists Tool Calls). It frames the point conceptually — *your agent stays yours; the only Composio-side LLM usage is optional and sandbox-scoped.* **Follow-up surfaces (not in this PR — see below):** this same clarification could be mirrored on the dashboard usage/billing UI and the marketing pricing page when an "LLM tokens" line item actually surfaces there. Those live outside this repo. # How did I test this PR - Docs-only change (single `.mdx` file); no code or dependency surface. - Verified all anchor targets referenced in the new callout exist on the same page / site: - `#built-in-helpers` → `### Built-in helpers` (the `invoke_llm` row) - `#error-correction` → `### Error correction` - `/docs/configuring-sessions` (existing page; documents `sandbox: { enable: true }`) - Matches the existing `<Callout title="...">` component usage already on the page (the "Renamed from workbench" callout), so it renders consistently in Fumadocs. - Confirmed against source that `invoke_llm` (docs `Built-in helpers` table) is the Composio-side LLM entry point and that the sandbox is opt-in via the `sandbox`/`workbench` session key. # Security - **Scope:** documentation-only change — one `.mdx` file, no dependencies, lockfiles, or executable code added/changed. - **Socket / Grype:** not applicable to this diff (no package manifests or code paths introduced); no new fixable CRITICAL/HIGH/MEDIUM findings possible from a Markdown copy addition. Triggered by: palash@composio.dev | Source: slack Session: https://zen.corp.composio.io/dashboard/#/chat/zen-f6a81a5a6764 --------- Co-authored-by: Zen Agent <zen@composio.dev> Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>

composio-zen[bot] committed Aug 3, 2026 at 20:46 UTC 8dcc9b991410968f7c425bd9d535d476bb8928f1
1 file changed +4
docs/content/docs/sandbox/remote.mdx
+4
@@ -10,6 +10,10 @@ The **sandbox** is a persistent Python environment where your agent writes and e
10 This feature used to be called the **workbench**. The preferred session config key is now `sandbox`, but `workbench` still works as a fully supported alias, in both SDKs and on the wire. It isn't deprecated, so existing code keeps running unchanged. The `COMPOSIO_REMOTE_WORKBENCH` and `COMPOSIO_REMOTE_BASH_TOOL` meta tools keep their names.
11 </Callout>
12
13 +<Callout title="Composio doesn't run or replace your agent">
14 +Your agent and its model stay entirely yours — Composio never proxies your LLM or runs an agent on your behalf. It discovers, authenticates, and executes tools. The one place Composio itself can call a model is *inside the sandbox*, and only when your code opts in — most directly through the [`invoke_llm`](#built-in-helpers) helper. That optional, sandbox-only usage is the sole source of any Composio-side **LLM tokens**. The sandbox is opt-in per [session](/docs/configuring-sessions) via `sandbox: { enable: true }` — don't enable it (or simply never call `invoke_llm`) and Composio uses no LLM tokens at all.
15 +</Callout>
16 +
17 ## Where it fits
18
19 Use the sandbox when a task is too complex for individual tool calls. Your agent starts with [`SEARCH_TOOLS` to find the right tools, then uses `MULTI_EXECUTE`](/docs/how-composio-works#meta-tools) for straightforward calls. When the task involves bulk operations, data transformations, or multi-step logic, the agent reaches for `COMPOSIO_REMOTE_WORKBENCH` instead.