Skip to content

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: add session creation FAQ to users-and-sessions and common FAQs

Sushmithamallesh0a37ffb2ff72
diff --git a/docs/content/docs/common-faq.mdx b/docs/content/docs/common-faq.mdx
index aac3b6dc6..4d4f14b9e 100644
--- a/docs/content/docs/common-faq.mdx
+++ b/docs/content/docs/common-faq.mdx
@@ -142,6 +142,10 @@ Composio does not have fixed IP ranges. Traffic is routed through Cloudflare and
<Accordion title="How do I increase my quota?">
Upgrade your plan. See [pricing](https://composio.dev/pricing) for available plans and limits.
</Accordion>
+<Accordion title="When should I create a new session?">
+Create a new session when the config changes: different toolkits, different auth config, or a different connected account. You don't need to store or manage session IDs. Just call `create()` each time. See [Users and sessions](/docs/users-and-sessions).
+</Accordion>
+
<Accordion title="How do I configure sessions with custom auth configs?">
Some toolkits require your own OAuth credentials or API keys. Create an auth config in the dashboard by selecting the toolkit, choosing the auth scheme, and entering your credentials. Then pass the auth config ID when creating a session using the `auth_configs` (or `auth_config_id`) parameter so the session uses your developer credentials instead of Composio-managed auth. See [Using custom auth configuration](/docs/using-custom-auth-configuration).
</Accordion>
diff --git a/docs/content/docs/users-and-sessions.mdx b/docs/content/docs/users-and-sessions.mdx
index 8960ec0ed..667ad4c1e 100644
--- a/docs/content/docs/users-and-sessions.mdx
+++ b/docs/content/docs/users-and-sessions.mdx
@@ -113,6 +113,12 @@ This means the boundary for a new session isn't a new chat or a new request. It'
Connections are tied to the user ID, not the session. A user who connected Gmail in one session can access it in every future session without re-authenticating.
+<Accordions>
+<Accordion title="When should I create a new session?">
+Create a new session when the config changes: different toolkits, different auth config, or a different connected account. You don't need to store or manage session IDs. Just call `create()` each time.
+</Accordion>
+</Accordions>
+
<Cards>
<Card icon={<BookOpen />} title="Configuring Sessions" href="/docs/configuring-sessions" description="Enable toolkits, set auth configs, and select connected accounts" />
<Card icon={<BookOpen />} title="Workbench" href="/docs/workbench" description="Write and run code in a persistent sandbox" />