@devries-cameron20 / composio Mirror · read-only / commits / fa627af4c
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 22, 18:15 UTC

auth page redo

Sushmithamallesh committed Dec 8, 2025 at 20:44 UTC fa627af4c1d86441ff2c345104b0ae311adfc291
1 file changed +12 -26
fern/pages/src/tool-router/authentication.mdx
+12 -26
@@ -6,53 +6,39 @@ keywords: "authentication, tool router, oauth, api key, connected accounts"
6 hide-nav-links: false
7 ---
8
9 -Tool Router automatically generates [Connect Link](/docs/authenticating-tools#hosted-authentication-connect-link) URLs when tools require authentication. Users complete OAuth or enter credentials on this hosted page.
9 +Tool Router handles authentication through [Connect Links](/docs/authenticating-tools#hosted-authentication-connect-link), hosted pages where users complete OAuth or enter credentials.
10
11 ## In-chat authentication
12
13 -By default, Tool Router includes the `COMPOSIO_MANAGE_CONNECTIONS` meta-tool. When the agent tries to execute a tool and the user hasn't connected that account, the agent prompts them with a Connect Link URL.
13 +By default, when a tool requires authentication, the agent prompts the user with a Connect Link. The user authenticates and confirms in chat.
14
15 -The user clicks the link, authenticates in the hosted UI, and confirms in chat. The agent then retries the action.
16 -
17 -This flow works well for chat applications where users interact directly with the agent. For details on configuring this flow, see [Using in-chat authentication](/tool-router/using-in-chat-authentication).
15 +This flow works well for chat applications where users interact directly with the agent. See [Using in-chat authentication](/tool-router/using-in-chat-authentication).
16
17 ## Manual authentication
18
21 -For applications that manage authentication outside of chat, disable in-chat auth and use `session.authorize()` to generate Connect Link URLs.
22 -
23 -This flow works well for:
24 -- Pre-authenticating users before they start chatting
25 -- Building custom connection UIs
19 +For apps that manage auth outside of chat, use `session.authorize()` to generate Connect Links programmatically.
20
27 -For implementation details, see [Manually authenticating users](/tool-router/manually-authenticating-users).
21 +Use this when you want users to connect accounts during onboarding, or when building a custom connections page. See [Manually authenticating users](/tool-router/manually-authenticating-users).
22
23 ## How Tool Router manages auth configs
24
25 When executing a tool, Tool Router needs an auth config to find or create a connected account. It handles this automatically:
26
33 -1. If you provide an `authConfigs` override, it uses that
34 -2. Otherwise, it looks for an auth config it previously created for this toolkit
35 -3. If none exists, it creates one using Composio managed auth and tags it for reuse
36 -4. Future sessions automatically reuse that auth config
27 +1. Uses your `authConfigs` override if provided
28 +2. Otherwise, reuses an auth config it previously created for this toolkit
29 +3. If none exists, creates one using Composio managed auth
30
38 -This means you don't need to create auth configs manually for most toolkits. Tool Router creates and manages them for you.
31 +You don't need to create auth configs manually for most toolkits.
32
33 ## Supported auth methods
34
42 -Tool Router can automatically create auth configs for:
43 -
44 -- **Composio managed OAuth** - GitHub, Gmail, Slack, and most OAuth toolkits. Composio provides the OAuth credentials.
45 -- **API key auth** - Users provide their own API keys via Connect Link.
35 +Tool Router supports **Composio managed OAuth** (GitHub, Gmail, Slack, and most toolkits) and **API key auth** (users enter their own keys via Connect Link).
36
37 <Note>
48 -Toolkits without Composio managed auth require you to create an auth config first. See [Configuring custom auth configs](/docs/tool-router/configuring-custom-auth-configs).
38 +Toolkits without Composio managed auth require a custom auth config. See [Configuring custom auth configs](/tool-router/configuring-custom-auth-configs).
39 </Note>
40
41 ## White-labeling
42
53 -To show your own branding on OAuth consent screens instead of Composio's, create your own OAuth app and pass the auth config ID in your session. See [White-labeling authentication](/tool-router/white-labeling-authentication).
54 -
55 -<Tip>
56 -For step-by-step guides on creating OAuth apps for specific services, see [composio.dev/auth](https://composio.dev/auth).
57 -</Tip>
43 +Show your own branding on OAuth consent screens by creating your own OAuth app. See [White-labeling authentication](/tool-router/white-labeling-authentication).
44