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

docs: note that create() always returns a new session ID

Previously create() would return the same session ID for identical configs. Now it always returns a new one for better isolation and observability. Updated guidance to use composio.use() for multi-turn. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Abir Taheer committed May 8, 2026 at 02:45 UTC 19a62962e9f1344558db0283f02ccb8867b48b4c
1 file changed +4 -2
docs/content/docs/users-and-sessions.mdx
+4 -2
@@ -103,9 +103,11 @@ const toolkits = await session.toolkits();
103
104 ## How sessions behave
105
106 -A session ties together a user, a set of available toolkits, auth configuration for those toolkits, and connected accounts. Call `create()` whenever you want to do a task. Each session is designed for a particular agentic task, and if you want to change the context of the task, create a new session.
106 +A session ties together a user, a set of available toolkits, auth configuration for those toolkits, and connected accounts. Each session is designed for a particular agentic task.
107
108 -You don't need to cache session IDs, manage session lifetimes, or worry about expiration. Sessions persist on the server and don't expire. Just call `create()` with what you need.
108 +Every call to `create()` returns a new session ID, even if the configuration is identical. This gives you clean isolation between tasks and makes it easy to trace activity back to a specific session in logs and analytics.
109 +
110 +Sessions persist on the server and don't expire. For multi-turn conversations, store the session ID and reuse it with `composio.use()` rather than calling `create()` again.
111
112 ### Reusing a session
113