@devries-cameron20 / composio Mirror · read-only / commits / ccce09474
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, 11:00 UTC

docs: clarify session defaults

Brendan O'Leary committed Sep 21, 2026 at 20:50 UTC ccce0947400c6aa78ad2b759350c385de0dad7b6
3 files changed +4 -2
docs/content/docs/how-composio-works.mdx
+1 -1
@@ -39,7 +39,7 @@ A session scopes four things:
39
40
41 ## What comes in a session
42 -Every session is designed to come with all of the things you will need for an agentic run for your user. By default, the session will come with all of the [tools and toolkits](#tools-and-toolkits), [authentication](#authentication) (for the given user) and skills needed to execute. Every session also comes with an agent [sandbox](#sandbox) so the agent can handle and manipulate large response, files, etc. outside of the context window for longer responses.
42 +By default, a session gives your agent meta tools to discover and execute app tools and manage connections for your user. All toolkits are discoverable, and search includes skill guidance when a matching skill exists. Standard sessions also include a [sandbox](#sandbox) for processing files and large responses outside the model's context window. You can restrict tool access or disable the sandbox through [session configuration](/docs/configuring-sessions).
43
44 Later we'll discuss [configuring sessions](/docs/configuring-sessions) for specialized use cases. But for now you can think of the Composio session as the basic building block for your agent.
45
docs/content/docs/quickstart.mdx
+2
@@ -38,6 +38,8 @@ The current Python package is `composio`. The package `composio-core` is the leg
38 </Callout>
39 </Tab>
40 <Tab value="TypeScript">
41 +The TypeScript SDK is ESM-only and requires **Node.js 22.22.3 or newer**. Use `import` syntax rather than CommonJS `require()`.
42 +
43 <PackageInstall
44 packages="@composio/core @composio/openai-agents @openai/agents"
45 comment={[
docs/content/docs/sandbox/remote.mdx
+1 -1
@@ -11,7 +11,7 @@ This feature used to be called the **workbench**. The preferred session config k
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.
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*, when your code opts in through the [`invoke_llm`](#built-in-helpers) helper. That optional sandbox usage is the sole source of Composio-side **LLM tokens**. Standard sessions enable the sandbox by default, and you can [disable it](/docs/configuring-sessions#disabling-the-sandbox). Sandbox access alone does not use LLM tokens.
15 </Callout>
16
17 ## Where it fits