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: lead the execution comparison with the reader question
Brendan O'Leary committed
Nov 11, 2026 at 17:05 UTC
639c2a8470054845ae93d42f6d72e31d0ad0c6f7
1 file changed
+2
docs/content/docs/sessions-vs-direct-execution.mdx
+2
@@ -5,6 +5,8 @@ keywords: [session, direct execution, tool router, meta tools, architecture, dec
5
legacy: true
6
---
7
8
+## Should I use sessions or direct execution?
9
+
10
A **session** is the runtime context Composio creates for one of your users with `composio.create(userId)`. It ties together the user, available toolkits, auth, and connected accounts. By default it gives your agent [meta tools](/docs/how-composio-works#meta-tools) so the agent discovers which app tools to use, authenticates users, and executes tools at runtime.
11
12
**Direct execution** skips the session. Your code fetches specific tool schemas, manages auth itself, and calls `tools.execute()` directly.