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: restore auth pages to the sidebar as an Authentication folder

Kshitij Jhunjhunwala5ca29e857e24
diff --git a/docs/agent/instructions/context.md b/docs/agent/instructions/context.md
index fc6bd0a99..91752397c 100644
--- a/docs/agent/instructions/context.md
+++ b/docs/agent/instructions/context.md
@@ -19,14 +19,14 @@ This is your always-on map of Composio's concepts and the canonical page for eac
## Authentication
- **How auth works** — Composio uses Connect Links (hosted auth pages) and **auth configs** (per-toolkit blueprints) to create **connected accounts** (stored credentials) scoped to a userID. This is the page for "how does authentication work". → [Authentication](/docs/authentication)
-- **Auth schemes / modes** — a toolkit's auth config uses one of `OAUTH2`, `API_KEY`, `BEARER_TOKEN`, or `BASIC`. When you mention a toolkit's auth mode, link the reference rather than explaining it inline. → [Auth schemes](/reference/api-reference/auth-configs#auth-schemes) for what each mode is and when it's used, [Authentication](/docs/authentication) for how auth works overall, and [Managed vs custom auth](/docs/custom-app-vs-managed-app) for choosing or bringing your own scheme.
+- **Auth schemes / modes** — a toolkit's auth config uses one of `OAUTH2`, `API_KEY`, `BEARER_TOKEN`, or `BASIC`. When you mention a toolkit's auth mode, link the reference rather than explaining it inline. → [Auth schemes](/reference/api-reference/auth-configs#auth-schemes) for what each mode is and when it's used, [Authentication](/docs/authentication) for how auth works overall, and [Managed vs custom auth](/docs/authentication/custom-app-vs-managed-app) for choosing or bringing your own scheme.
- **In-chat auth** — the agent prompts the user to connect via `COMPOSIO_MANAGE_CONNECTIONS`. → [In-chat authentication](/docs/authenticating-users/in-chat-authentication)
- **Manual auth** — generate Connect Links yourself with `session.authorize()`. → [Manually authenticating users](/docs/authenticating-users/manually-authenticating)
-- **Managed vs custom auth** — use Composio's managed OAuth apps, or bring your own for branding/scopes. → [Managed vs custom auth](/docs/custom-app-vs-managed-app)
-- **White-labeling** — remove Composio branding from the auth flow. → [White-labeling authentication](/docs/white-labeling-authentication)
+- **Managed vs custom auth** — use Composio's managed OAuth apps, or bring your own for branding/scopes. → [Managed vs custom auth](/docs/authentication/custom-app-vs-managed-app)
+- **White-labeling** — remove Composio branding from the auth flow. → [White-labeling authentication](/docs/authentication/white-labeling-authentication)
- **Callback identity verification** — opt-in per-project defense against OAuth session fixation, documented in the connected-accounts API overview: set a verifier URL and Composio holds each OAuth connection until the developer's server confirms the returning user (`complete_auth`); once set it covers every OAuth connection in the project. This is the section for "connections from the dashboard stopped completing" and "a real `user_id` is now required". → [Callback identity verification](/reference/api-reference/connected-accounts#callback-identity-verification)
-- **Importing existing connections** — pass in API keys or bearer tokens you already hold. → [Importing existing connections](/docs/importing-existing-connections)
-- **Multiple accounts per user** — e.g. work and personal Gmail. → [Managing multiple connected accounts](/docs/managing-multiple-connected-accounts)
+- **Importing existing connections** — pass in API keys or bearer tokens you already hold. → [Importing existing connections](/docs/authentication/importing-existing-connections)
+- **Multiple accounts per user** — e.g. work and personal Gmail. → [Managing multiple connected accounts](/docs/authentication/managing-multiple-connected-accounts)
- **Shared connections** — share one connected account across users via an ACL. → [Shared connections](/docs/authenticating-users/shared-connections)
## Triggers and webhooks
diff --git a/docs/api-overviews/auth-configs.mdx b/docs/api-overviews/auth-configs.mdx
index 966e5ac16..b0e147819 100644
--- a/docs/api-overviews/auth-configs.mdx
+++ b/docs/api-overviews/auth-configs.mdx
@@ -8,7 +8,7 @@ Each auth config defines:
- **Scopes**: what your tools are allowed to do on the user's behalf
- **Credentials**: Composio's managed app, or your own OAuth client and secrets
-Reach for a custom auth config when you need your own branding on consent screens, custom scopes, a dedicated rate-limit quota, or a custom toolkit instance. See [managed vs custom auth](/docs/custom-app-vs-managed-app) for the decision and [how Composio handles authentication](/docs/authentication) for the full picture.
+Reach for a custom auth config when you need your own branding on consent screens, custom scopes, a dedicated rate-limit quota, or a custom toolkit instance. See [managed vs custom auth](/docs/authentication/custom-app-vs-managed-app) for the decision and [how Composio handles authentication](/docs/authentication) for the full picture.
## Auth schemes
@@ -21,6 +21,6 @@ The `auth_scheme` on an auth config determines how users authenticate to the too
| `BEARER_TOKEN` | A bearer access token you already hold (for example, from your own OAuth flow). Composio sends it as `Authorization: Bearer <token>` and does not refresh it, so you keep it current. | Bringing an existing OAuth or server-to-server token into Composio, or apps that issue long-lived tokens. |
| `BASIC` | HTTP Basic authentication with a username and password. | Services that use Basic Auth. |
-Most OAuth toolkits work out of the box with Composio managed auth. For the others you supply the credential fields. To choose or customize the scheme, see [managed vs custom auth](/docs/custom-app-vs-managed-app).
+Most OAuth toolkits work out of the box with Composio managed auth. For the others you supply the credential fields. To choose or customize the scheme, see [managed vs custom auth](/docs/authentication/custom-app-vs-managed-app).
These endpoints use your project API key in the `x-api-key` header. Each auth config is addressed by its `nanoid`, and you can enable or disable one without deleting it.
diff --git a/docs/api-overviews/connected-accounts.mdx b/docs/api-overviews/connected-accounts.mdx
index 29cfa9af3..8899426d8 100644
--- a/docs/api-overviews/connected-accounts.mdx
+++ b/docs/api-overviews/connected-accounts.mdx
@@ -2,7 +2,7 @@ A connected account is a single user's authorized connection to a toolkit. It st
Composio creates a connected account when a user completes the flow defined by an [auth config](/reference/api-reference/auth-configs). From there you manage its full lifecycle:
-- **Create or link**: start a new connection, or generate an auth link session for the user to authorize. See [manually authenticating users](/docs/manually-authenticating).
+- **Create or link**: start a new connection, or generate an auth link session for the user to authorize. See [manually authenticating users](/docs/authentication/manually-authenticating).
- **Refresh**: renew authentication for an account whose tokens have expired.
- **Enable, disable, or update**: change an account's status or metadata without removing it.
- **Revoke or delete**: revoke the grant at the provider, or remove the account from Composio.
@@ -13,7 +13,7 @@ Each account is addressed by its `nanoid`. List endpoints accept filters so you
A Composio Connect Link is a hosted, secure sign-in page. You create one with the create auth link session endpoint, redirect the user to the returned URL, and Composio handles the rest: the user signs in, Composio creates the connected account, and Composio stores and refreshes its tokens. Credentials never pass through your app. This works for all Composio managed connections, with no OAuth credentials to set up.
-By default a connected account is `PRIVATE` and usable only by its owning user. Mark one `SHARED` to let other users reach it through a per-connection access control list. See [shared connections](/docs/shared-connections).
+By default a connected account is `PRIVATE` and usable only by its owning user. Mark one `SHARED` to let other users reach it through a per-connection access control list. See [shared connections](/docs/extending-sessions/shared-connections).
These endpoints use your project API key in the `x-api-key` header.
diff --git a/docs/app/layout.tsx b/docs/app/layout.tsx
index 90bf3da77..bf78d106b 100644
--- a/docs/app/layout.tsx
+++ b/docs/app/layout.tsx
@@ -13,7 +13,7 @@ const defaultLinkSlugs: { slug: string[]; source: typeof source }[] = [
{ slug: ['quickstart'], source },
{ slug: ['authentication'], source },
{ slug: ['configuring-sessions'], source },
- { slug: ['white-labeling-authentication'], source },
+ { slug: ['authentication', 'white-labeling-authentication'], source },
{ slug: ['glossary'], source: referenceSource },
{ slug: ['troubleshooting'], source },
];
diff --git a/docs/app/llms.mdx/[[...slug]]/route.ts b/docs/app/llms.mdx/[[...slug]]/route.ts
index ff483c3b2..557e3c6ac 100644
--- a/docs/app/llms.mdx/[[...slug]]/route.ts
+++ b/docs/app/llms.mdx/[[...slug]]/route.ts
@@ -946,7 +946,7 @@ async function generateManagedAuthIndex(): Promise<string> {
" -H 'x-api-key: YOUR_API_KEY'",
'```',
'',
- 'See [When to use your own developer credentials](/docs/custom-app-vs-managed-app.md) for help deciding which approach fits your use case.',
+ 'See [When to use your own developer credentials](/docs/authentication/custom-app-vs-managed-app.md) for help deciding which approach fits your use case.',
'',
`## Composio Managed App Available (${managed.length})`,
'',
diff --git a/docs/app/llms.txt/route.ts b/docs/app/llms.txt/route.ts
index 2b48cd6a8..5ae09e2d6 100644
--- a/docs/app/llms.txt/route.ts
+++ b/docs/app/llms.txt/route.ts
@@ -100,17 +100,6 @@ function formatPage(page: { url: string }) {
return `- https://docs.composio.dev${page.url}.md`;
}
-const AUTHENTICATION_GUIDE_URLS = [
- '/docs/manually-authenticating',
- '/docs/managing-multiple-connected-accounts',
- '/docs/shared-connections',
- '/docs/importing-existing-connections',
- '/docs/custom-app-vs-managed-app',
- '/docs/programmatic-auth-configs',
- '/docs/controlling-scopes',
- '/docs/white-labeling-authentication',
-];
-
/**
* Splits reference pages by REST version.
*
@@ -165,10 +154,6 @@ ${legacyReferencePages.map(formatPage).join('\n')}
${docsTree}
-## Authentication guides
-
-${AUTHENTICATION_GUIDE_URLS.map(url => formatPage({ url })).join('\n')}
-
## Examples
${examplesPages.map(formatPage).join('\n')}
diff --git a/docs/content/changelog/03-13-26-polling-interval-grace-period.mdx b/docs/content/changelog/03-13-26-polling-interval-grace-period.mdx
index 55f9a2c6c..62351fe84 100644
--- a/docs/content/changelog/03-13-26-polling-interval-grace-period.mdx
+++ b/docs/content/changelog/03-13-26-polling-interval-grace-period.mdx
@@ -28,4 +28,4 @@ Set up **your own OAuth app**. With custom auth:
OAuth approval from Google, Microsoft, etc. takes **days to weeks**. Start now.
</Callout>
-→ [Set up your own OAuth app](/docs/custom-app-vs-managed-app)
\ No newline at end of file
+→ [Set up your own OAuth app](/docs/authentication/custom-app-vs-managed-app)
\ No newline at end of file
diff --git a/docs/content/changelog/04-07-26-bearer-token-patch.mdx b/docs/content/changelog/04-07-26-bearer-token-patch.mdx
index e450cb750..454445cbc 100644
--- a/docs/content/changelog/04-07-26-bearer-token-patch.mdx
+++ b/docs/content/changelog/04-07-26-bearer-token-patch.mdx
@@ -22,7 +22,7 @@ BEARER_TOKEN is injected as an alternative scheme alongside OAuth2, so existing
Creating bearer token auth configs is currently available only via API and SDK — not yet supported in the dashboard UI.
</Callout>
-See the [importing connections guide](/docs/importing-existing-connections) for full examples.
+See the [importing connections guide](/docs/authentication/importing-existing-connections) for full examples.
## Credential Patching
diff --git a/docs/content/changelog/04-09-26-multi-account-aliases.mdx b/docs/content/changelog/04-09-26-multi-account-aliases.mdx
index 290b3c911..65ce16ae3 100644
--- a/docs/content/changelog/04-09-26-multi-account-aliases.mdx
+++ b/docs/content/changelog/04-09-26-multi-account-aliases.mdx
@@ -45,4 +45,4 @@ await composio.connectedAccounts.update('ca_abc123', { alias: 'work-gmail' });
Aliases must be unique per user and toolkit within a project.
-See the [multi-account guide](/docs/managing-multiple-connected-accounts) for full details.
+See the [multi-account guide](/docs/authentication/managing-multiple-connected-accounts) for full details.
diff --git a/docs/content/changelog/04-28-26-sdk-link-allow-multiple.mdx b/docs/content/changelog/04-28-26-sdk-link-allow-multiple.mdx
index a2cf6623f..7a5ae6471 100644
--- a/docs/content/changelog/04-28-26-sdk-link-allow-multiple.mdx
+++ b/docs/content/changelog/04-28-26-sdk-link-allow-multiple.mdx
@@ -52,7 +52,7 @@ const connectionRequest = await composio.connectedAccounts.link(
</Tab>
</Tabs>
-Pair with a session-level `multiAccount` / `multi_account` config so the agent can disambiguate at execution time. See [Managing multiple connected accounts](/docs/managing-multiple-connected-accounts) for the session shape.
+Pair with a session-level `multiAccount` / `multi_account` config so the agent can disambiguate at execution time. See [Managing multiple connected accounts](/docs/authentication/managing-multiple-connected-accounts) for the session shape.
**2. You're migrating from `initiate()` to `link()`** as part of the [Composio-managed OAuth migration](/docs/changelog/2026/04/24). Pass `allow_multiple` / `allowMultiple` through unchanged — same flag name, same default (`False`), same exception (`ComposioMultipleConnectedAccountsError`).
diff --git a/docs/content/changelog/05-08-26-session-use-update-connected-accounts.mdx b/docs/content/changelog/05-08-26-session-use-update-connected-accounts.mdx
index 8c251c60c..4327dd2f3 100644
--- a/docs/content/changelog/05-08-26-session-use-update-connected-accounts.mdx
+++ b/docs/content/changelog/05-08-26-session-use-update-connected-accounts.mdx
@@ -101,7 +101,7 @@ const session = await composio.create("user_123", {
</Tab>
</Tabs>
-Only one account per toolkit is allowed when [multi-account mode](/docs/managing-multiple-connected-accounts) is disabled.
+Only one account per toolkit is allowed when [multi-account mode](/docs/authentication/managing-multiple-connected-accounts) is disabled.
### SDK versions
diff --git a/docs/content/docs/auth-configuration/connected-accounts.mdx b/docs/content/docs/auth-configuration/connected-accounts.mdx
index 5f87902bd..3abd0242c 100644
--- a/docs/content/docs/auth-configuration/connected-accounts.mdx
+++ b/docs/content/docs/auth-configuration/connected-accounts.mdx
@@ -7,7 +7,7 @@ legacy: true
---
<Callout type="info">
-If you're building an agent, we recommend using [sessions](/docs/configuring-sessions) instead. See [Managing multiple connected accounts](/docs/managing-multiple-connected-accounts) for how sessions handle account selection automatically.
+If you're building an agent, we recommend using [sessions](/docs/configuring-sessions) instead. See [Managing multiple connected accounts](/docs/authentication/managing-multiple-connected-accounts) for how sessions handle account selection automatically.
</Callout>
Connected accounts are authenticated connections between your users and toolkits. After users authenticate (see [Authenticating tools](/docs/tools-direct/authenticating-tools)), you can manage these accounts throughout their lifecycle.
@@ -319,7 +319,7 @@ try {
</Tabs>
<Callout type="info">
-For session-based apps, see [Managing multiple connected accounts](/docs/managing-multiple-connected-accounts) for how to pass a specific account to a session.
+For session-based apps, see [Managing multiple connected accounts](/docs/authentication/managing-multiple-connected-accounts) for how to pass a specific account to a session.
</Callout>
### Execute with a specific account
diff --git a/docs/content/docs/auth-configuration/custom-auth-configs.mdx b/docs/content/docs/auth-configuration/custom-auth-configs.mdx
index af3cbedc3..2771278e2 100644
--- a/docs/content/docs/auth-configuration/custom-auth-configs.mdx
+++ b/docs/content/docs/auth-configuration/custom-auth-configs.mdx
@@ -7,7 +7,7 @@ legacy: true
---
<Callout type="info">
-If you're building an agent, we recommend using [sessions](/docs/configuring-sessions) instead. See [Managed vs custom auth](/docs/custom-app-vs-managed-app) for how to use custom credentials with sessions.
+If you're building an agent, we recommend using [sessions](/docs/configuring-sessions) instead. See [Managed vs custom auth](/docs/authentication/custom-app-vs-managed-app) for how to use custom credentials with sessions.
</Callout>
Auth configs control how users authenticate with a toolkit. By default, Composio provides managed credentials for many toolkits. You create a custom auth config when the defaults don't fit your needs.
diff --git a/docs/content/docs/auth-configuration/custom-auth-params.mdx b/docs/content/docs/auth-configuration/custom-auth-params.mdx
index f9a405bfd..45aa87b53 100644
--- a/docs/content/docs/auth-configuration/custom-auth-params.mdx
+++ b/docs/content/docs/auth-configuration/custom-auth-params.mdx
@@ -7,7 +7,7 @@ legacy: true
---
<Callout type="info">
-If you're building an agent, we recommend using [sessions](/docs/configuring-sessions) instead. Sessions handle authentication automatically via [in-chat authentication](/docs/authentication#in-chat-authentication) or [manual authentication](/docs/manually-authenticating).
+If you're building an agent, we recommend using [sessions](/docs/configuring-sessions) instead. Sessions handle authentication automatically via [in-chat authentication](/docs/authentication#in-chat-authentication) or [manual authentication](/docs/authentication/manually-authenticating).
</Callout>
If you already manage OAuth tokens or API keys yourself and want Composio to execute tools using your credentials, you can pass them directly at execution time — no connected account or redirect flow required.
diff --git a/docs/content/docs/auth-configuration/white-labeling.mdx b/docs/content/docs/auth-configuration/white-labeling.mdx
index 51f99da61..d452ee116 100644
--- a/docs/content/docs/auth-configuration/white-labeling.mdx
+++ b/docs/content/docs/auth-configuration/white-labeling.mdx
@@ -7,7 +7,7 @@ legacy: true
---
<Callout type="info">
-If you're building an agent with sessions, see [White-labeling authentication](/docs/white-labeling-authentication) instead.
+If you're building an agent with sessions, see [White-labeling authentication](/docs/authentication/white-labeling-authentication) instead.
</Callout>
There are four places where Composio branding shows up during authentication:
diff --git a/docs/content/docs/controlling-scopes.mdx b/docs/content/docs/authentication/controlling-scopes.mdx
similarity index 97%
rename from docs/content/docs/controlling-scopes.mdx
rename to docs/content/docs/authentication/controlling-scopes.mdx
index 32740149b..878fc435a 100644
--- a/docs/content/docs/controlling-scopes.mdx
+++ b/docs/content/docs/authentication/controlling-scopes.mdx
@@ -150,4 +150,4 @@ const session = await composio.create('user_123', {
## Next
-<Card icon={<Palette />} title="White-labeling authentication" href="/docs/white-labeling-authentication" description="Remove Composio branding from your auth flows" />
+<Card icon={<Palette />} title="White-labeling authentication" href="/docs/authentication/white-labeling-authentication" description="Remove Composio branding from your auth flows" />
diff --git a/docs/content/docs/custom-app-vs-managed-app.mdx b/docs/content/docs/authentication/custom-app-vs-managed-app.mdx
similarity index 94%
rename from docs/content/docs/custom-app-vs-managed-app.mdx
rename to docs/content/docs/authentication/custom-app-vs-managed-app.mdx
index 877379cbe..e60ddd273 100644
--- a/docs/content/docs/custom-app-vs-managed-app.mdx
+++ b/docs/content/docs/authentication/custom-app-vs-managed-app.mdx
@@ -17,7 +17,7 @@ Managed apps are the default. Every toolkit that supports OAuth has a Composio m
- **You're building and iterating.** No OAuth app registration, no credentials to manage. Create a session and start testing immediately.
- **Default scopes cover your needs.** Composio requests sensible defaults for each toolkit.
-- **Branding on consent screens doesn't matter yet.** Users will see "Composio wants to access your account" during OAuth. Fine for internal tools, prototypes, and development. You can still [white-label the Connect Link page](/docs/white-labeling-authentication#customizing-the-connect-link) with your logo and app title without needing your own OAuth app.
+- **Branding on consent screens doesn't matter yet.** Users will see "Composio wants to access your account" during OAuth. Fine for internal tools, prototypes, and development. You can still [white-label the Connect Link page](/docs/authentication/white-labeling-authentication#customizing-the-connect-link) with your logo and app title without needing your own OAuth app.
## When to use a custom auth config
@@ -34,7 +34,7 @@ Bring your own credentials when any of these apply:
To check whether a toolkit already has a Composio managed app, see the [managed auth toolkit list](/toolkits/managed-auth). You can still create a custom auth config for branding, scopes, rate limits, polling intervals, or custom instances.
-The steps below use the dashboard. To create auth configs in code instead, for example one per customer, see [Programmatic auth configs](/docs/programmatic-auth-configs).
+The steps below use the dashboard. To create auth configs in code instead, for example one per customer, see [Programmatic auth configs](/docs/authentication/programmatic-auth-configs).
<Steps>
<Step>
@@ -142,4 +142,4 @@ Some toolkits don't have Composio managed auth. For these, the setup is the same
## Next
-<Card icon={<Code />} title="Programmatic auth configs" href="/docs/programmatic-auth-configs" description="Create auth configs in code and pass them to a session" />
+<Card icon={<Code />} title="Programmatic auth configs" href="/docs/authentication/programmatic-auth-configs" description="Create auth configs in code and pass them to a session" />
diff --git a/docs/content/docs/importing-existing-connections.mdx b/docs/content/docs/authentication/importing-existing-connections.mdx
similarity index 95%
rename from docs/content/docs/importing-existing-connections.mdx
rename to docs/content/docs/authentication/importing-existing-connections.mdx
index f333d78fa..4d0d880e6 100644
--- a/docs/content/docs/importing-existing-connections.mdx
+++ b/docs/content/docs/authentication/importing-existing-connections.mdx
@@ -17,7 +17,7 @@ This is useful when:
## Prerequisites
-1. **An [auth config](/docs/programmatic-auth-configs)** for the toolkit you're importing into
+1. **An [auth config](/docs/authentication/programmatic-auth-configs)** for the toolkit you're importing into
2. **The existing credentials** for each user (API keys, bearer tokens, username/password, etc.)
3. **A userID** for each user. Any string that uniquely identifies them in your system.
@@ -74,7 +74,7 @@ If you manage your own OAuth flow and already have an access token for a service
Since you're providing your own token, Composio won't handle OAuth refresh. You're responsible for refreshing the token on your end and pushing the updated value to Composio via the [PATCH method](#updating-credentials) whenever it changes.
-After [creating an auth config](/docs/programmatic-auth-configs) with `authScheme: "BEARER_TOKEN"`, use the snippet below to create a connected account:
+After [creating an auth config](/docs/authentication/programmatic-auth-configs) with `authScheme: "BEARER_TOKEN"`, use the snippet below to create a connected account:
<Tabs groupId="language" items={['Python', 'TypeScript']} persist>
<Tab value="Python">
@@ -326,4 +326,4 @@ const session = await composio.create('user_123', {
## Next
-<Card icon={<Database />} title="Managing multiple accounts" href="/docs/managing-multiple-connected-accounts" description="Pin and select connected accounts for a user" />
+<Card icon={<Database />} title="Managing multiple accounts" href="/docs/authentication/managing-multiple-connected-accounts" description="Pin and select connected accounts for a user" />
diff --git a/docs/content/docs/authentication.mdx b/docs/content/docs/authentication/index.mdx
similarity index 78%
rename from docs/content/docs/authentication.mdx
rename to docs/content/docs/authentication/index.mdx
index 4ddfc7d39..27e45c9eb 100644
--- a/docs/content/docs/authentication.mdx
+++ b/docs/content/docs/authentication/index.mdx
@@ -29,7 +29,7 @@ Every session includes the [`COMPOSIO_MANAGE_CONNECTIONS`](/toolkits/meta-tools/
The user signs in on the hosted link and Composio stores the resulting connected account. Credentials never pass through your app or the model, so it's safe to surface the link right in the chat.
-You only need a [custom auth config](/docs/custom-app-vs-managed-app) to bring your own OAuth app, request specific scopes, or use a toolkit without managed auth.
+You only need a [custom auth config](/docs/authentication/custom-app-vs-managed-app) to bring your own OAuth app, request specific scopes, or use a toolkit without managed auth.
## In-chat authentication
@@ -83,7 +83,7 @@ const session = await composio.create("user_123", {
Don't want to wait for the agent? Call `session.authorize()` to generate a Connect Link on demand, for onboarding, a settings page, or a pre-flight check before a task.
-<Card icon={<ShieldCheck />} title="Manual auth management" href="/docs/manually-authenticating">
+<Card icon={<ShieldCheck />} title="Manual auth management" href="/docs/authentication/manually-authenticating">
`session.authorize()`, callback URLs, connection status, and disabling in-chat prompts
</Card>
@@ -95,7 +95,7 @@ Composio manages authentication with **auth configs**. An [auth config](/referen
- **Scopes**: what actions your tools can perform
- **Credentials**: your own app credentials, or Composio's managed auth
-Composio creates one auth config per toolkit and applies it to every user who connects that toolkit. Most toolkits use Composio managed auth, so you don't create or configure anything. You only need a [custom auth config](/docs/custom-app-vs-managed-app) to use your own OAuth app or customize scopes.
+Composio creates one auth config per toolkit and applies it to every user who connects that toolkit. Most toolkits use Composio managed auth, so you don't create or configure anything. You only need a [custom auth config](/docs/authentication/custom-app-vs-managed-app) to use your own OAuth app or customize scopes.
<AuthConfigFlow />
@@ -136,12 +136,12 @@ console.log(connectionRequest.redirectUrl);
## Authentication guides
<Cards>
- <Card title="Manual auth management" href="/docs/manually-authenticating" description="Generate Connect Links yourself, check connection status, and disable in-chat prompts." />
- <Card title="Multiple connected accounts" href="/docs/managing-multiple-connected-accounts" description="Let one user choose between work, personal, or other accounts." />
- <Card title="Shared connections" href="/docs/shared-connections" description="Share one connected account with a controlled set of users." />
- <Card title="Import existing connections" href="/docs/importing-existing-connections" description="Bring credentials your application already stores into Composio." />
- <Card title="Managed vs custom auth" href="/docs/custom-app-vs-managed-app" description="Decide whether to use Composio credentials or your own OAuth app." />
- <Card title="Programmatic auth configs" href="/docs/programmatic-auth-configs" description="Create auth configs in code and attach them to sessions." />
- <Card title="Control OAuth scopes" href="/docs/controlling-scopes" description="Choose the permissions requested when a user connects." />
- <Card title="White-label authentication" href="/docs/white-labeling-authentication" description="Use your own OAuth app and remove Composio branding." />
+ <Card title="Manual auth management" href="/docs/authentication/manually-authenticating" description="Generate Connect Links yourself, check connection status, and disable in-chat prompts." />
+ <Card title="Multiple connected accounts" href="/docs/authentication/managing-multiple-connected-accounts" description="Let one user choose between work, personal, or other accounts." />
+ <Card title="Shared connections" href="/docs/extending-sessions/shared-connections" description="Share one connected account with a controlled set of users." />
+ <Card title="Import existing connections" href="/docs/authentication/importing-existing-connections" description="Bring credentials your application already stores into Composio." />
+ <Card title="Managed vs custom auth" href="/docs/authentication/custom-app-vs-managed-app" description="Decide whether to use Composio credentials or your own OAuth app." />
+ <Card title="Programmatic auth configs" href="/docs/authentication/programmatic-auth-configs" description="Create auth configs in code and attach them to sessions." />
+ <Card title="Control OAuth scopes" href="/docs/authentication/controlling-scopes" description="Choose the permissions requested when a user connects." />
+ <Card title="White-label authentication" href="/docs/authentication/white-labeling-authentication" description="Use your own OAuth app and remove Composio branding." />
</Cards>
diff --git a/docs/content/docs/managing-multiple-connected-accounts.mdx b/docs/content/docs/authentication/managing-multiple-connected-accounts.mdx
similarity index 98%
rename from docs/content/docs/managing-multiple-connected-accounts.mdx
rename to docs/content/docs/authentication/managing-multiple-connected-accounts.mdx
index 0436c5d78..bbd82afd4 100644
--- a/docs/content/docs/managing-multiple-connected-accounts.mdx
+++ b/docs/content/docs/authentication/managing-multiple-connected-accounts.mdx
@@ -220,4 +220,4 @@ for (const toolkit of toolkits.items) {
## Next
-<Card icon={<Database />} title="Shared connections" href="/docs/shared-connections" description="Make one connected account usable by multiple users with a per-user access control list" />
+<Card icon={<Database />} title="Shared connections" href="/docs/extending-sessions/shared-connections" description="Make one connected account usable by multiple users with a per-user access control list" />
diff --git a/docs/content/docs/manually-authenticating.mdx b/docs/content/docs/authentication/manually-authenticating.mdx
similarity index 97%
rename from docs/content/docs/manually-authenticating.mdx
rename to docs/content/docs/authentication/manually-authenticating.mdx
index 370de43ab..59fc04edb 100644
--- a/docs/content/docs/manually-authenticating.mdx
+++ b/docs/content/docs/authentication/manually-authenticating.mdx
@@ -215,4 +215,4 @@ console.log("All toolkits connected!");
## Next
-<Card icon={<Database />} title="Managing multiple connected accounts" href="/docs/managing-multiple-connected-accounts" description="Let a user connect work and personal accounts for the same toolkit, then pick which one runs" />
+<Card icon={<Database />} title="Managing multiple connected accounts" href="/docs/authentication/managing-multiple-connected-accounts" description="Let a user connect work and personal accounts for the same toolkit, then pick which one runs" />
diff --git a/docs/content/docs/authentication/meta.json b/docs/content/docs/authentication/meta.json
new file mode 100644
index 000000000..19c262892
--- /dev/null
+++ b/docs/content/docs/authentication/meta.json
@@ -0,0 +1,13 @@
+{
+ "title": "Authentication",
+ "pages": [
+ "index",
+ "manually-authenticating",
+ "managing-multiple-connected-accounts",
+ "importing-existing-connections",
+ "custom-app-vs-managed-app",
+ "programmatic-auth-configs",
+ "controlling-scopes",
+ "white-labeling-authentication"
+ ]
+}
diff --git a/docs/content/docs/programmatic-auth-configs.mdx b/docs/content/docs/authentication/programmatic-auth-configs.mdx
similarity index 96%
rename from docs/content/docs/programmatic-auth-configs.mdx
rename to docs/content/docs/authentication/programmatic-auth-configs.mdx
index 5d8b7ad44..a5f3c97d1 100644
--- a/docs/content/docs/programmatic-auth-configs.mdx
+++ b/docs/content/docs/authentication/programmatic-auth-configs.mdx
@@ -95,7 +95,7 @@ const authConfig = await composio.authConfigs.create('notion', {
</Tabs>
<Callout type="info">
-Omit `oauth_redirect_uri` to use Composio's default callback. Set it only when you [route the callback through your own domain](/docs/white-labeling-authentication#routing-the-callback-through-your-domain).
+Omit `oauth_redirect_uri` to use Composio's default callback. Set it only when you [route the callback through your own domain](/docs/authentication/white-labeling-authentication#routing-the-callback-through-your-domain).
</Callout>
## Other auth types
@@ -211,4 +211,4 @@ console.log(fields);
## Next
-<Card icon={<Key />} title="Controlling scopes" href="/docs/controlling-scopes" description="Override the default OAuth scopes Composio requests for a toolkit" />
+<Card icon={<Key />} title="Controlling scopes" href="/docs/authentication/controlling-scopes" description="Override the default OAuth scopes Composio requests for a toolkit" />
diff --git a/docs/content/docs/white-labeling-authentication.mdx b/docs/content/docs/authentication/white-labeling-authentication.mdx
similarity index 92%
rename from docs/content/docs/white-labeling-authentication.mdx
rename to docs/content/docs/authentication/white-labeling-authentication.mdx
index 38c9fee6f..d519c506d 100644
--- a/docs/content/docs/white-labeling-authentication.mdx
+++ b/docs/content/docs/authentication/white-labeling-authentication.mdx
@@ -22,7 +22,7 @@ To replace it with your own branding:
1. Go to **Project Settings** → [**Auth Screen**](https://dashboard.composio.dev/~/project/settings/auth-screen?utm_source=docs&utm_medium=content&utm_campaign=docs-white-labeling-authentication)
2. Upload your **Logo** and set your **App Title**
-This applies to all Connect Link flows across all toolkits, for both [in-chat](/docs/authentication#in-chat-authentication) and [manual](/docs/manually-authenticating) authentication. Each project has one logo and app title, so if you need different branding per product, use separate projects.
+This applies to all Connect Link flows across all toolkits, for both [in-chat](/docs/authentication#in-chat-authentication) and [manual](/docs/authentication/manually-authenticating) authentication. Each project has one logo and app title, so if you need different branding per product, use separate projects.
<Callout>
Customizing the Connect Link only changes the Composio-hosted page. For OAuth toolkits like Gmail, Google Sheets, GitHub, and Slack, users still see a consent screen saying "Composio wants to access your account." To change that, and to remove the "Secured by Composio" badge, set up your own OAuth app as described [below](#using-your-own-oauth-apps).
@@ -42,7 +42,7 @@ OAuth toolkits like Google and GitHub show a consent screen that says which app
Only white-label toolkits where users see a consent screen (Google, GitHub, Slack, etc.). Toolkits that use API keys don't show consent screens, so there's nothing to white-label. You can mix and match freely.
</Callout>
-<Card icon={<Key />} title="Managed vs custom auth" href="/docs/custom-app-vs-managed-app" description="Decide when to use custom credentials, create an auth config, and pass it to sessions." />
+<Card icon={<Key />} title="Managed vs custom auth" href="/docs/authentication/custom-app-vs-managed-app" description="Decide when to use custom credentials, create an auth config, and pass it to sessions." />
### Switching from Composio-managed to your own OAuth app
@@ -150,8 +150,8 @@ const connectionRequest = await session.authorize("gmail", {
</Tab>
</Tabs>
-After authentication, Composio redirects the user to your callback URL instead of the default success page. For full details on the parameters appended to your callback URL, see [Manually authenticating users → Redirecting users after authentication](/docs/manually-authenticating#redirecting-users-after-authentication).
+After authentication, Composio redirects the user to your callback URL instead of the default success page. For full details on the parameters appended to your callback URL, see [Manually authenticating users → Redirecting users after authentication](/docs/authentication/manually-authenticating#redirecting-users-after-authentication).
## Next
-<Card icon={<Key />} title="Managed vs custom auth" href="/docs/custom-app-vs-managed-app" description="Set up auth configs for OAuth apps, API keys, and toolkits without managed auth" />
+<Card icon={<Key />} title="Managed vs custom auth" href="/docs/authentication/custom-app-vs-managed-app" description="Set up auth configs for OAuth apps, API keys, and toolkits without managed auth" />
diff --git a/docs/content/docs/configuring-sessions.mdx b/docs/content/docs/configuring-sessions.mdx
index 9cbf0859b..88b285145 100644
--- a/docs/content/docs/configuring-sessions.mdx
+++ b/docs/content/docs/configuring-sessions.mdx
@@ -441,7 +441,7 @@ Requires `@composio/core` ≥ `0.9.0` (TypeScript) or `composio` ≥ `0.13.0`
<Callout type="info">
`preload.tools` is not supported when `multiAccount.enable` is true. See
-[Managing multiple connected accounts](/docs/managing-multiple-connected-accounts).
+[Managing multiple connected accounts](/docs/authentication/managing-multiple-connected-accounts).
</Callout>
<Tabs groupId="language" items={['Python', 'TypeScript']} persist>
@@ -536,7 +536,7 @@ const session = await composio.create("user_123", {
</Tab>
</Tabs>
-See [White-labeling authentication](/docs/white-labeling-authentication) for branding, or [Managed vs custom auth](/docs/custom-app-vs-managed-app) for toolkits that require your own credentials.
+See [White-labeling authentication](/docs/authentication/white-labeling-authentication) for branding, or [Managed vs custom auth](/docs/authentication/custom-app-vs-managed-app) for toolkits that require your own credentials.
## Account selection
@@ -570,7 +570,7 @@ const session = await composio.create("user_123", {
</Tabs>
<Callout type="info">
-Arrays are the preferred format for `connectedAccounts`. A single string (e.g. `"ca_work_gmail"`) is still accepted for backwards compatibility and is automatically coerced to a single-element array. Only one account per toolkit is allowed when [multi-account mode](/docs/managing-multiple-connected-accounts) is disabled.
+Arrays are the preferred format for `connectedAccounts`. A single string (e.g. `"ca_work_gmail"`) is still accepted for backwards compatibility and is automatically coerced to a single-element array. Only one account per toolkit is allowed when [multi-account mode](/docs/authentication/managing-multiple-connected-accounts) is disabled.
</Callout>
### Precedence
@@ -731,7 +731,7 @@ const connectedAccount = await connectionRequest.waitForConnection();
</Tab>
</Tabs>
-For more details, see [Manually authenticating users](/docs/manually-authenticating).
+For more details, see [Manually authenticating users](/docs/authentication/manually-authenticating).
### toolkits()
diff --git a/docs/content/docs/extending-sessions/custom-mcp.mdx b/docs/content/docs/extending-sessions/custom-mcp.mdx
index cbe63a70e..3313742cd 100644
--- a/docs/content/docs/extending-sessions/custom-mcp.mdx
+++ b/docs/content/docs/extending-sessions/custom-mcp.mdx
@@ -409,5 +409,5 @@ See [Toolkit Versioning](/docs/tools-direct/toolkit-versioning) for more example
<Card title="Using sessions via MCP" href="/docs/sessions-via-mcp" description="Connect an MCP client to a Composio-hosted session" />
<Card title="Custom Tools and Toolkits" href="/docs/extending-sessions/custom-tools-and-toolkits" description="Run your own tools inside your application process" />
<Card title="Configuring Sessions" href="/docs/configuring-sessions" description="Configure toolkit and tool filtering" />
-<Card title="Managing Multiple Connected Accounts" href="/docs/managing-multiple-connected-accounts" description="Select a connected account explicitly" />
+<Card title="Managing Multiple Connected Accounts" href="/docs/authentication/managing-multiple-connected-accounts" description="Select a connected account explicitly" />
</Cards>
diff --git a/docs/content/docs/extending-sessions/meta.json b/docs/content/docs/extending-sessions/meta.json
index 68cd6f562..39bd49349 100644
--- a/docs/content/docs/extending-sessions/meta.json
+++ b/docs/content/docs/extending-sessions/meta.json
@@ -4,6 +4,7 @@
"pages": [
"proxy-execute",
"custom-tools-and-toolkits",
+ "shared-connections",
"custom-mcp"
]
}
diff --git a/docs/content/docs/extending-sessions/proxy-execute.mdx b/docs/content/docs/extending-sessions/proxy-execute.mdx
index 3bd30e1c7..346152ab5 100644
--- a/docs/content/docs/extending-sessions/proxy-execute.mdx
+++ b/docs/content/docs/extending-sessions/proxy-execute.mdx
@@ -101,7 +101,7 @@ Don't set the `Authorization` header yourself through `parameters`. Composio inj
| Status | Typical cause | How to resolve |
|---|---|---|
| `400 Bad Request` | Malformed endpoint path, invalid body, or unsupported `method`. | Check the upstream API docs for the expected shape. The proxy doesn't validate upstream schemas. |
-| `401 Unauthorized` | The connected account's token expired or was revoked. | Re-authenticate the user, or [import fresh credentials](/docs/importing-existing-connections). |
+| `401 Unauthorized` | The connected account's token expired or was revoked. | Re-authenticate the user, or [import fresh credentials](/docs/authentication/importing-existing-connections). |
| `403 Forbidden` | The user's OAuth scopes or API key don't cover this endpoint. | Update the [auth config scopes](/docs/auth-configuration/custom-auth-configs) and have the user re-consent. |
| `429 Too Many Requests` | Upstream rate limit (GitHub, Google, and so on). | Honor the `Retry-After` header and back off. Composio doesn't retry automatically. |
diff --git a/docs/content/docs/shared-connections.mdx b/docs/content/docs/extending-sessions/shared-connections.mdx
similarity index 100%
rename from docs/content/docs/shared-connections.mdx
rename to docs/content/docs/extending-sessions/shared-connections.mdx
diff --git a/docs/content/docs/how-composio-works.mdx b/docs/content/docs/how-composio-works.mdx
index da5dd0590..dd7f1e9f3 100644
--- a/docs/content/docs/how-composio-works.mdx
+++ b/docs/content/docs/how-composio-works.mdx
@@ -58,7 +58,7 @@ A user is an identifier from your app. Composio stores connections under that ID
</Accordion>
</Accordions>
-A user can connect multiple accounts for the same toolkit, like work and personal Gmail. Use the same userID, then select the connected account when a session needs a specific one. See [Managing multiple connected accounts](/docs/managing-multiple-connected-accounts).
+A user can connect multiple accounts for the same toolkit, like work and personal Gmail. Use the same userID, then select the connected account when a session needs a specific one. See [Managing multiple connected accounts](/docs/authentication/managing-multiple-connected-accounts).
## Meta tools
@@ -76,7 +76,7 @@ When a tool needs a connection, the session generates a Connect Link with `sessi
In chat, the agent can pause, ask the user to connect an app, then retry the tool once auth completes. Composio manages the OAuth redirects, token exchange, and refresh. Once a user connects a toolkit, the connected account persists and future sessions reuse it without re-authentication.
-For OAuth toolkits, Composio uses [managed apps](/docs/custom-app-vs-managed-app) by default. Bring your own app when you need your own branding, scopes, or consent screen.
+For OAuth toolkits, Composio uses [managed apps](/docs/authentication/custom-app-vs-managed-app) by default. Bring your own app when you need your own branding, scopes, or consent screen.
## Sandbox
diff --git a/docs/content/docs/meta.json b/docs/content/docs/meta.json
index 6c533cb54..0e7498bc8 100644
--- a/docs/content/docs/meta.json
+++ b/docs/content/docs/meta.json
@@ -22,8 +22,9 @@
"sessions-vs-direct-execution",
"tools-direct",
"auth-configuration",
- "---Migration and security---",
+ "---Migration---",
"migration-guide",
+ "---Security and data---",
"security"
]
}
diff --git a/docs/content/docs/migration-guide/direct-to-sessions.mdx b/docs/content/docs/migration-guide/direct-to-sessions.mdx
index ab0e8cd48..dd00c448f 100644
--- a/docs/content/docs/migration-guide/direct-to-sessions.mdx
+++ b/docs/content/docs/migration-guide/direct-to-sessions.mdx
@@ -264,7 +264,7 @@ const session = await composio.create("user_123", {
</Tab>
</Tabs>
-If you don't specify, the most recently connected account is used. See [Managing multiple connected accounts](/docs/managing-multiple-connected-accounts) for details.
+If you don't specify, the most recently connected account is used. See [Managing multiple connected accounts](/docs/authentication/managing-multiple-connected-accounts) for details.
## Triggers
@@ -276,7 +276,7 @@ See [Triggers](/docs/triggers) for setup instructions.
If you've set up white-labeled OAuth screens with custom auth configs, those carry over automatically. Just pass the same auth config IDs to your session via `auth_configs` / `authConfigs`. Your users will continue to see your branding on consent screens.
-See [White-labeling authentication](/docs/white-labeling-authentication) for more.
+See [White-labeling authentication](/docs/authentication/white-labeling-authentication) for more.
## Next
diff --git a/docs/content/docs/migration-guide/mcp-servers-to-sessions.mdx b/docs/content/docs/migration-guide/mcp-servers-to-sessions.mdx
index 61a770ed0..6bfb22814 100644
--- a/docs/content/docs/migration-guide/mcp-servers-to-sessions.mdx
+++ b/docs/content/docs/migration-guide/mcp-servers-to-sessions.mdx
@@ -238,11 +238,11 @@ const result = await session.execute("GITHUB_CREATE_ISSUE", {
session once and keep using it across calls; see [Configuring Sessions](/docs/configuring-sessions).
- **Sharing one account across users** — sessions support **shared connections**
(`account_type:"SHARED"` + an allow/deny ACL), pinned per session. See
- [Shared connections](/docs/shared-connections).
+ [Shared connections](/docs/extending-sessions/shared-connections).
- **Tenant-specific params** (SharePoint sub-site, Jira subdomain) — prefill them via shared
credentials on the auth config.
- **White-labeling carries over** — pass the same white-labeled auth config IDs; users keep seeing
- your branding on consent screens. See [White-labeling authentication](/docs/white-labeling-authentication).
+ your branding on consent screens. See [White-labeling authentication](/docs/authentication/white-labeling-authentication).
- **Triggers** — unchanged; continue using `composio.triggers.*` and webhooks (triggers aren't part
of sessions yet).
- **Dashboard** — sessions are created via the SDK. For no-code, personal app connections, use
diff --git a/docs/content/docs/migration-guide/new-sdk.mdx b/docs/content/docs/migration-guide/new-sdk.mdx
index ccbe291ed..5e456fe9a 100644
--- a/docs/content/docs/migration-guide/new-sdk.mdx
+++ b/docs/content/docs/migration-guide/new-sdk.mdx
@@ -736,7 +736,7 @@ console.log(authConfig);
</Tab>
</Tabs>
-For using custom authentication credentials, refer to the [Programmatic Auth Configs](/docs/programmatic-auth-configs) documentation.
+For using custom authentication credentials, refer to the [Programmatic Auth Configs](/docs/authentication/programmatic-auth-configs) documentation.
<Callout type="info">
The callback URL for creating custom OAuth configs is now `https://backend.composio.dev/api/v3/toolkits/auth/callback`. The previous URL was `https://backend.composio.dev/api/v1/auth-apps/add`.
diff --git a/docs/content/docs/sessions-vs-direct-execution.mdx b/docs/content/docs/sessions-vs-direct-execution.mdx
index 97a88f72d..e5b2a2bcc 100644
--- a/docs/content/docs/sessions-vs-direct-execution.mdx
+++ b/docs/content/docs/sessions-vs-direct-execution.mdx
@@ -17,7 +17,7 @@ Use sessions unless you need full control over which tools are available and whe
| **Context cost** | Only meta tools in context, app tools loaded on demand | Every tool schema you select is loaded upfront |
| **Guidance** | Search returns recommended steps and common pitfalls alongside schemas | You get tool schemas only |
| **Memory** | Meta tools share context across calls, storing discovered IDs and relationships | You manage state between calls |
-| **Auth** | [In-chat](/docs/authentication#in-chat-authentication): agent prompts the user to connect when needed. Also supports [manual](/docs/manually-authenticating) | You build the auth flow with [connect links](/docs/tools-direct/authenticating-tools) |
+| **Auth** | [In-chat](/docs/authentication#in-chat-authentication): agent prompts the user to connect when needed. Also supports [manual](/docs/authentication/manually-authenticating) | You build the auth flow with [connect links](/docs/tools-direct/authenticating-tools) |
| **[Sandbox](/docs/sandbox/remote)** | Built in, large responses offloaded automatically | Not available |
| **Human approval** | You configure approval rules on the session. Harder to intercept individual calls since tools are discovered dynamically | You intercept before each call in your code |
| **Latency** | Multiple LLM turns (search, then execute) | Single call |
diff --git a/docs/content/docs/tools-direct/authenticating-tools.mdx b/docs/content/docs/tools-direct/authenticating-tools.mdx
index 16065a577..98d57e359 100644
--- a/docs/content/docs/tools-direct/authenticating-tools.mdx
+++ b/docs/content/docs/tools-direct/authenticating-tools.mdx
@@ -7,7 +7,7 @@ legacy: true
---
<Callout type="info">
-If you're building an agent, we recommend using [sessions](/docs/configuring-sessions) instead. Sessions handle authentication automatically via [in-chat authentication](/docs/authentication#in-chat-authentication) or [manual authentication](/docs/manually-authenticating).
+If you're building an agent, we recommend using [sessions](/docs/configuring-sessions) instead. Sessions handle authentication automatically via [in-chat authentication](/docs/authentication#in-chat-authentication) or [manual authentication](/docs/authentication/manually-authenticating).
</Callout>
The first step in authenticating your users is to create an **Auth Config**. Every toolkit has its own authentication method such as `OAuth`, `API key`, `Basic Auth`, or custom schemes.
@@ -80,7 +80,7 @@ You should create multiple auth configs for the same toolkit when you need:
- **Different permission levels** - Limiting actions for specific use cases
<Cards>
- <Card title="Programmatic creation" href="/docs/programmatic-auth-configs">
+ <Card title="Programmatic creation" href="/docs/authentication/programmatic-auth-configs">
For managing auth configs across multiple projects, you can create them programmatically via the API
</Card>
<Card title="Production white-labeling" href="/docs/auth-configuration/white-labeling">
diff --git a/docs/content/examples/general-agent-with-pi.mdx b/docs/content/examples/general-agent-with-pi.mdx
index 0e73db1c4..5e5c90cdc 100644
--- a/docs/content/examples/general-agent-with-pi.mdx
+++ b/docs/content/examples/general-agent-with-pi.mdx
@@ -46,7 +46,7 @@ bun add @composio/core @composio/experimental @earendil-works/pi-coding-agent
## Install the bot
-A Slack bot needs a Slack app to authenticate as and a stream of events. Composio gives you both, so you never register a webhook with Slack or hold a bot token. The `slackbot` toolkit ships with Composio-managed OAuth, and you install it as one **[shared connection](/docs/shared-connections)** for the whole workspace.
+A Slack bot needs a Slack app to authenticate as and a stream of events. Composio gives you both, so you never register a webhook with Slack or hold a bot token. The `slackbot` toolkit ships with Composio-managed OAuth, and you install it as one **[shared connection](/docs/extending-sessions/shared-connections)** for the whole workspace.
This is `install.ts`, run once, built up three steps at a time:
@@ -106,5 +106,5 @@ Run `bun install.ts` once to set up the bot, start the server with `bun bot.ts`,
<Cards>
<Card title="Configuring sessions" href="/docs/configuring-sessions" description="Everything a session can scope: toolkits, tools, connections, and limits" />
- <Card title="Shared connections" href="/docs/shared-connections" description="SHARED vs PRIVATE accounts and the per-user ACL" />
+ <Card title="Shared connections" href="/docs/extending-sessions/shared-connections" description="SHARED vs PRIVATE accounts and the per-user ACL" />
</Cards>
diff --git a/docs/content/examples/standup-slackbot.mdx b/docs/content/examples/standup-slackbot.mdx
index b01c33f96..a4e049459 100644
--- a/docs/content/examples/standup-slackbot.mdx
+++ b/docs/content/examples/standup-slackbot.mdx
@@ -27,8 +27,8 @@ This is a deliberately advanced, opinionated build. It's a strong reference for
- **Background-agent sessions**: the draft agent runs on a schedule, not in a conversation. It works from the tools a member already connected and never pauses to ask for auth.
- **Manual execution for deterministic workflows**: outside the draft, the bot doesn't let an agent decide. It runs a fixed flow, calling tools directly with [manual execution](/docs/tools-direct/executing-tools), so a button always triggers the same exact steps.
-- **Manual, pre-connected auth**: members connect their tools ahead of time using [manual connections](/docs/manually-authenticating), and the agent just uses whatever is there.
-- **White-labelling** (advanced): your own Slack app and bot identity, via [white-labelling](/docs/white-labeling-authentication). This is *not* the easy path. We'd recommend Composio's managed apps, which require no additional configuration. Only do this if you specifically want your own branding.
+- **Manual, pre-connected auth**: members connect their tools ahead of time using [manual connections](/docs/authentication/manually-authenticating), and the agent just uses whatever is there.
+- **White-labelling** (advanced): your own Slack app and bot identity, via [white-labelling](/docs/authentication/white-labeling-authentication). This is *not* the easy path. We'd recommend Composio's managed apps, which require no additional configuration. Only do this if you specifically want your own branding.
- **The proxy** (advanced): using [`proxyExecute`](/docs/extending-sessions/proxy-execute) to call Slack API endpoints Composio doesn't wrap as tools.
It is **not** an example of [in-chat or dynamic auth](/docs/authentication) (asking a user to connect a tool mid-run), and it's more setup than many bots need. If you'd rather have a Slack bot with zero setup (Composio's managed app) or in-chat auth, start with the [general Slack bot](/examples/general-agent-with-pi) instead.
@@ -61,7 +61,7 @@ This bot doesn't post as "Composio". It posts as *my* app, with its own name, ic
<Figure src="/images/standup-slackbot/bot-avatar.png" alt="The Daily Standup Bot avatar" size="sm" />
-That's [white-labelling](/docs/white-labeling-authentication): you bring your own Slack app's credentials instead of using Composio-managed ones. Composio-managed auth needs no setup at all; white-labelling is the trade-off, you register and configure your own Slack app first. It's more work, but the bot is fully yours.
+That's [white-labelling](/docs/authentication/white-labeling-authentication): you bring your own Slack app's credentials instead of using Composio-managed ones. Composio-managed auth needs no setup at all; white-labelling is the trade-off, you register and configure your own Slack app first. It's more work, but the bot is fully yours.
Slack's app-creation UI changes from time to time, so the exact screens below may differ. First, the Slack app itself.
@@ -87,7 +87,7 @@ Slack's app-creation UI changes from time to time, so the exact screens below ma
## Auth the bot
-The Slack app exists; now connect it through Composio so your code can act as it. You create one `slackbot` auth config from your credentials, then a setup script does the OAuth once with Composio's [manual authentication](/docs/manually-authenticating) flow.
+The Slack app exists; now connect it through Composio so your code can act as it. You create one `slackbot` auth config from your credentials, then a setup script does the OAuth once with Composio's [manual authentication](/docs/authentication/manually-authenticating) flow.
<Callout type="info" title="`slackbot` vs `slack`" className="[&_ul]:my-2 [&_ul]:list-disc [&_ul]:pl-5 [&_li]:my-1 [&_li]:pl-1">
@@ -224,7 +224,7 @@ The bot posts the result back as a draft the member can confirm or edit:
Edit `standup.config.ts` with your team (each member's Slack email and timezone, plus your channel and GitHub org), set your four environment variables, run `npx tsx scripts/setup.ts` once to connect your bot, then `vercel deploy`.
<Cards>
<Card title="Configuring sessions" href="/docs/configuring-sessions" description="What a session can scope: toolkits, tools, connections, and connection management" />
- <Card title="White-labeling authentication" href="/docs/white-labeling-authentication" description="Ship a bot under your own app's name, icon, and credentials" />
- <Card title="Custom vs managed auth" href="/docs/custom-app-vs-managed-app" description="Bring-your-own Slack app versus a Composio-managed connection" />
+ <Card title="White-labeling authentication" href="/docs/authentication/white-labeling-authentication" description="Ship a bot under your own app's name, icon, and credentials" />
+ <Card title="Custom vs managed auth" href="/docs/authentication/custom-app-vs-managed-app" description="Bring-your-own Slack app versus a Composio-managed connection" />
<Card title="Triggers" href="/docs/triggers" description="Run agents in response to events: schedules, webhooks, and app activity" />
</Cards>
diff --git a/docs/content/reference/api-reference/auth-configs/index.mdx b/docs/content/reference/api-reference/auth-configs/index.mdx
index 1b01d636e..86304a996 100644
--- a/docs/content/reference/api-reference/auth-configs/index.mdx
+++ b/docs/content/reference/api-reference/auth-configs/index.mdx
@@ -15,7 +15,7 @@ Each auth config defines:
- **Scopes**: what your tools are allowed to do on the user's behalf
- **Credentials**: Composio's managed app, or your own OAuth client and secrets
-Reach for a custom auth config when you need your own branding on consent screens, custom scopes, a dedicated rate-limit quota, or a custom toolkit instance. See [managed vs custom auth](/docs/custom-app-vs-managed-app) for the decision and [how Composio handles authentication](/docs/authentication) for the full picture.
+Reach for a custom auth config when you need your own branding on consent screens, custom scopes, a dedicated rate-limit quota, or a custom toolkit instance. See [managed vs custom auth](/docs/authentication/custom-app-vs-managed-app) for the decision and [how Composio handles authentication](/docs/authentication) for the full picture.
## Auth schemes
@@ -28,7 +28,7 @@ The `auth_scheme` on an auth config determines how users authenticate to the too
| `BEARER_TOKEN` | A bearer access token you already hold (for example, from your own OAuth flow). Composio sends it as `Authorization: Bearer <token>` and does not refresh it, so you keep it current. | Bringing an existing OAuth or server-to-server token into Composio, or apps that issue long-lived tokens. |
| `BASIC` | HTTP Basic authentication with a username and password. | Services that use Basic Auth. |
-Most OAuth toolkits work out of the box with Composio managed auth. For the others you supply the credential fields. To choose or customize the scheme, see [managed vs custom auth](/docs/custom-app-vs-managed-app).
+Most OAuth toolkits work out of the box with Composio managed auth. For the others you supply the credential fields. To choose or customize the scheme, see [managed vs custom auth](/docs/authentication/custom-app-vs-managed-app).
These endpoints use your project API key in the `x-api-key` header. Each auth config is addressed by its `nanoid`, and you can enable or disable one without deleting it.
diff --git a/docs/content/reference/api-reference/connected-accounts/index.mdx b/docs/content/reference/api-reference/connected-accounts/index.mdx
index 2cb152521..adca22c74 100644
--- a/docs/content/reference/api-reference/connected-accounts/index.mdx
+++ b/docs/content/reference/api-reference/connected-accounts/index.mdx
@@ -9,7 +9,7 @@ A connected account is a single user's authorized connection to a toolkit. It st
Composio creates a connected account when a user completes the flow defined by an [auth config](/reference/api-reference/auth-configs). From there you manage its full lifecycle:
-- **Create or link**: start a new connection, or generate an auth link session for the user to authorize. See [manually authenticating users](/docs/manually-authenticating).
+- **Create or link**: start a new connection, or generate an auth link session for the user to authorize. See [manually authenticating users](/docs/authentication/manually-authenticating).
- **Refresh**: renew authentication for an account whose tokens have expired.
- **Enable, disable, or update**: change an account's status or metadata without removing it.
- **Revoke or delete**: revoke the grant at the provider, or remove the account from Composio.
@@ -20,7 +20,7 @@ Each account is addressed by its `nanoid`. List endpoints accept filters so you
A Composio Connect Link is a hosted, secure sign-in page. You create one with the create auth link session endpoint, redirect the user to the returned URL, and Composio handles the rest: the user signs in, Composio creates the connected account, and Composio stores and refreshes its tokens. Credentials never pass through your app. This works for all Composio managed connections, with no OAuth credentials to set up.
-By default a connected account is `PRIVATE` and usable only by its owning user. Mark one `SHARED` to let other users reach it through a per-connection access control list. See [shared connections](/docs/shared-connections).
+By default a connected account is `PRIVATE` and usable only by its owning user. Mark one `SHARED` to let other users reach it through a per-connection access control list. See [shared connections](/docs/extending-sessions/shared-connections).
These endpoints use your project API key in the `x-api-key` header.
diff --git a/docs/content/reference/glossary.mdx b/docs/content/reference/glossary.mdx
index d2f6e93a5..fa815da3b 100644
--- a/docs/content/reference/glossary.mdx
+++ b/docs/content/reference/glossary.mdx
@@ -32,7 +32,7 @@ A hosted page where a user authorizes access to a toolkit. It is returned as a `
</GlossaryTerm>
<GlossaryTerm name="Connected Account">
-A stored set of credentials (OAuth tokens or API keys) linked to a userID, created when a user authenticates with a toolkit. Composio refreshes OAuth tokens automatically, and a user can have [multiple connected accounts](/docs/managing-multiple-connected-accounts) for the same toolkit. IDs are prefixed `ca_`.
+A stored set of credentials (OAuth tokens or API keys) linked to a userID, created when a user authenticates with a toolkit. Composio refreshes OAuth tokens automatically, and a user can have [multiple connected accounts](/docs/authentication/managing-multiple-connected-accounts) for the same toolkit. IDs are prefixed `ca_`.
</GlossaryTerm>
<GlossaryTerm name="Connection Request">
@@ -52,7 +52,7 @@ An open protocol for connecting AI models to external tools. Create a session wi
</GlossaryTerm>
<GlossaryTerm name="Manual Authentication">
-Authenticating users from your own code with `session.authorize()` or `connectedAccounts.link()`, rather than letting the agent handle it through in-chat authentication. See [Manual authentication](/docs/manually-authenticating).
+Authenticating users from your own code with `session.authorize()` or `connectedAccounts.link()`, rather than letting the agent handle it through in-chat authentication. See [Manual authentication](/docs/authentication/manually-authenticating).
</GlossaryTerm>
<GlossaryTerm name="Meta Tools">
@@ -136,7 +136,7 @@ An identifier from your application that Composio uses to scope connected accoun
</GlossaryTerm>
<GlossaryTerm name="White-Labeling">
-Customizing the auth experience so users see your brand during the OAuth flow. You provide your own OAuth credentials, redirect URIs, and branding. See [White-labeling authentication](/docs/white-labeling-authentication).
+Customizing the auth experience so users see your brand during the OAuth flow. You provide your own OAuth credentials, redirect URIs, and branding. See [White-labeling authentication](/docs/authentication/white-labeling-authentication).
</GlossaryTerm>
<GlossaryTerm name="Sandbox">
diff --git a/docs/content/reference/v3/api-reference/auth-configs/index.mdx b/docs/content/reference/v3/api-reference/auth-configs/index.mdx
index b820a5c37..9bc165110 100644
--- a/docs/content/reference/v3/api-reference/auth-configs/index.mdx
+++ b/docs/content/reference/v3/api-reference/auth-configs/index.mdx
@@ -15,7 +15,7 @@ Each auth config defines:
- **Scopes**: what your tools are allowed to do on the user's behalf
- **Credentials**: Composio's managed app, or your own OAuth client and secrets
-Reach for a custom auth config when you need your own branding on consent screens, custom scopes, a dedicated rate-limit quota, or a custom toolkit instance. See [managed vs custom auth](/docs/custom-app-vs-managed-app) for the decision and [how Composio handles authentication](/docs/authentication) for the full picture.
+Reach for a custom auth config when you need your own branding on consent screens, custom scopes, a dedicated rate-limit quota, or a custom toolkit instance. See [managed vs custom auth](/docs/authentication/custom-app-vs-managed-app) for the decision and [how Composio handles authentication](/docs/authentication) for the full picture.
## Auth schemes
@@ -28,7 +28,7 @@ The `auth_scheme` on an auth config determines how users authenticate to the too
| `BEARER_TOKEN` | A bearer access token you already hold (for example, from your own OAuth flow). Composio sends it as `Authorization: Bearer <token>` and does not refresh it, so you keep it current. | Bringing an existing OAuth or server-to-server token into Composio, or apps that issue long-lived tokens. |
| `BASIC` | HTTP Basic authentication with a username and password. | Services that use Basic Auth. |
-Most OAuth toolkits work out of the box with Composio managed auth. For the others you supply the credential fields. To choose or customize the scheme, see [managed vs custom auth](/docs/custom-app-vs-managed-app).
+Most OAuth toolkits work out of the box with Composio managed auth. For the others you supply the credential fields. To choose or customize the scheme, see [managed vs custom auth](/docs/authentication/custom-app-vs-managed-app).
These endpoints use your project API key in the `x-api-key` header. Each auth config is addressed by its `nanoid`, and you can enable or disable one without deleting it.
diff --git a/docs/content/reference/v3/api-reference/connected-accounts/index.mdx b/docs/content/reference/v3/api-reference/connected-accounts/index.mdx
index fcc9cc6cd..f8458f739 100644
--- a/docs/content/reference/v3/api-reference/connected-accounts/index.mdx
+++ b/docs/content/reference/v3/api-reference/connected-accounts/index.mdx
@@ -9,7 +9,7 @@ A connected account is a single user's authorized connection to a toolkit. It st
Composio creates a connected account when a user completes the flow defined by an [auth config](/reference/api-reference/auth-configs). From there you manage its full lifecycle:
-- **Create or link**: start a new connection, or generate an auth link session for the user to authorize. See [manually authenticating users](/docs/manually-authenticating).
+- **Create or link**: start a new connection, or generate an auth link session for the user to authorize. See [manually authenticating users](/docs/authentication/manually-authenticating).
- **Refresh**: renew authentication for an account whose tokens have expired.
- **Enable, disable, or update**: change an account's status or metadata without removing it.
- **Revoke or delete**: revoke the grant at the provider, or remove the account from Composio.
@@ -20,7 +20,7 @@ Each account is addressed by its `nanoid`. List endpoints accept filters so you
A Composio Connect Link is a hosted, secure sign-in page. You create one with the create auth link session endpoint, redirect the user to the returned URL, and Composio handles the rest: the user signs in, Composio creates the connected account, and Composio stores and refreshes its tokens. Credentials never pass through your app. This works for all Composio managed connections, with no OAuth credentials to set up.
-By default a connected account is `PRIVATE` and usable only by its owning user. Mark one `SHARED` to let other users reach it through a per-connection access control list. See [shared connections](/docs/shared-connections).
+By default a connected account is `PRIVATE` and usable only by its owning user. Mark one `SHARED` to let other users reach it through a per-connection access control list. See [shared connections](/docs/extending-sessions/shared-connections).
These endpoints use your project API key in the `x-api-key` header.
diff --git a/docs/content/toolkits/faq/gmail.md b/docs/content/toolkits/faq/gmail.md
index 99f8f25ba..ad3239bcf 100644
--- a/docs/content/toolkits/faq/gmail.md
+++ b/docs/content/toolkits/faq/gmail.md
@@ -14,11 +14,11 @@ When using custom OAuth credentials, the Gmail API must be enabled in the Google
## Why am I getting "Error 400: invalid_scope"?
-The requested scopes are invalid or incorrectly formatted in the authorization URL. Verify your scope values against the [Google OAuth scopes docs](https://developers.google.com/identity/protocols/oauth2). If you're creating auth configs programmatically, see the [programmatic auth config guide](/docs/programmatic-auth-configs).
+The requested scopes are invalid or incorrectly formatted in the authorization URL. Verify your scope values against the [Google OAuth scopes docs](https://developers.google.com/identity/protocols/oauth2). If you're creating auth configs programmatically, see the [programmatic auth config guide](/docs/authentication/programmatic-auth-configs).
## Why does the OAuth consent screen show "Composio" instead of my app?
-By default, the consent screen uses Composio's OAuth app. To show your own app name and logo, create your own OAuth app and set a custom redirect URL. See [White-labeling authentication](/docs/white-labeling-authentication#using-your-own-oauth-apps).
+By default, the consent screen uses Composio's OAuth app. To show your own app name and logo, create your own OAuth app and set a custom redirect URL. See [White-labeling authentication](/docs/authentication/white-labeling-authentication#using-your-own-oauth-apps).
## Why am I getting 401 errors on tool calls?
diff --git a/docs/content/toolkits/faq/google_classroom.md b/docs/content/toolkits/faq/google_classroom.md
index a21069b5d..b425fc57c 100644
--- a/docs/content/toolkits/faq/google_classroom.md
+++ b/docs/content/toolkits/faq/google_classroom.md
@@ -14,11 +14,11 @@ When using custom OAuth credentials, the Google Classroom API must be enabled in
## Why am I getting "Error 400: invalid_scope"?
-The requested scopes are invalid or incorrectly formatted in the authorization URL. Verify your scope values against the [Google OAuth scopes docs](https://developers.google.com/identity/protocols/oauth2). If you're creating auth configs programmatically, see the [programmatic auth config guide](/docs/programmatic-auth-configs).
+The requested scopes are invalid or incorrectly formatted in the authorization URL. Verify your scope values against the [Google OAuth scopes docs](https://developers.google.com/identity/protocols/oauth2). If you're creating auth configs programmatically, see the [programmatic auth config guide](/docs/authentication/programmatic-auth-configs).
## Why does the OAuth consent screen show "Composio" instead of my app?
-By default, the consent screen uses Composio's OAuth app. To show your own app name and logo, create your own OAuth app and set a custom redirect URL. See [White-labeling authentication](/docs/white-labeling-authentication#using-your-own-oauth-apps).
+By default, the consent screen uses Composio's OAuth app. To show your own app name and logo, create your own OAuth app and set a custom redirect URL. See [White-labeling authentication](/docs/authentication/white-labeling-authentication#using-your-own-oauth-apps).
## Why am I getting 401 errors on tool calls?
diff --git a/docs/content/toolkits/faq/google_maps.md b/docs/content/toolkits/faq/google_maps.md
index 8d22333dd..e264f4740 100644
--- a/docs/content/toolkits/faq/google_maps.md
+++ b/docs/content/toolkits/faq/google_maps.md
@@ -14,11 +14,11 @@ When using custom OAuth credentials, the Google Maps API must be enabled in the
## Why am I getting "Error 400: invalid_scope"?
-The requested scopes are invalid or incorrectly formatted in the authorization URL. Verify your scope values against the [Google OAuth scopes docs](https://developers.google.com/identity/protocols/oauth2). If you're creating auth configs programmatically, see the [programmatic auth config guide](/docs/programmatic-auth-configs).
+The requested scopes are invalid or incorrectly formatted in the authorization URL. Verify your scope values against the [Google OAuth scopes docs](https://developers.google.com/identity/protocols/oauth2). If you're creating auth configs programmatically, see the [programmatic auth config guide](/docs/authentication/programmatic-auth-configs).
## Why does the OAuth consent screen show "Composio" instead of my app?
-By default, the consent screen uses Composio's OAuth app. To show your own app name and logo, create your own OAuth app and set a custom redirect URL. See [White-labeling authentication](/docs/white-labeling-authentication#using-your-own-oauth-apps).
+By default, the consent screen uses Composio's OAuth app. To show your own app name and logo, create your own OAuth app and set a custom redirect URL. See [White-labeling authentication](/docs/authentication/white-labeling-authentication#using-your-own-oauth-apps).
## Why am I getting 401 errors on tool calls?
diff --git a/docs/content/toolkits/faq/googlecalendar.md b/docs/content/toolkits/faq/googlecalendar.md
index 35a2abc53..d76c551cc 100644
--- a/docs/content/toolkits/faq/googlecalendar.md
+++ b/docs/content/toolkits/faq/googlecalendar.md
@@ -14,11 +14,11 @@ When using custom OAuth credentials, the Google Calendar API must be enabled in
## Why am I getting "Error 400: invalid_scope"?
-The requested scopes are invalid or incorrectly formatted in the authorization URL. Verify your scope values against the [Google OAuth scopes docs](https://developers.google.com/identity/protocols/oauth2). If you're creating auth configs programmatically, see the [programmatic auth config guide](/docs/programmatic-auth-configs).
+The requested scopes are invalid or incorrectly formatted in the authorization URL. Verify your scope values against the [Google OAuth scopes docs](https://developers.google.com/identity/protocols/oauth2). If you're creating auth configs programmatically, see the [programmatic auth config guide](/docs/authentication/programmatic-auth-configs).
## Why does the OAuth consent screen show "Composio" instead of my app?
-By default, the consent screen uses Composio's OAuth app. To show your own app name and logo, create your own OAuth app and set a custom redirect URL. See [White-labeling authentication](/docs/white-labeling-authentication#using-your-own-oauth-apps).
+By default, the consent screen uses Composio's OAuth app. To show your own app name and logo, create your own OAuth app and set a custom redirect URL. See [White-labeling authentication](/docs/authentication/white-labeling-authentication#using-your-own-oauth-apps).
## Why am I getting 401 errors on tool calls?
diff --git a/docs/content/toolkits/faq/googledocs.md b/docs/content/toolkits/faq/googledocs.md
index 0b1d8c01d..cdd97a97e 100644
--- a/docs/content/toolkits/faq/googledocs.md
+++ b/docs/content/toolkits/faq/googledocs.md
@@ -14,11 +14,11 @@ When using custom OAuth credentials, the Google Docs API must be enabled in the
## Why am I getting "Error 400: invalid_scope"?
-The requested scopes are invalid or incorrectly formatted in the authorization URL. Verify your scope values against the [Google OAuth scopes docs](https://developers.google.com/identity/protocols/oauth2). If you're creating auth configs programmatically, see the [programmatic auth config guide](/docs/programmatic-auth-configs).
+The requested scopes are invalid or incorrectly formatted in the authorization URL. Verify your scope values against the [Google OAuth scopes docs](https://developers.google.com/identity/protocols/oauth2). If you're creating auth configs programmatically, see the [programmatic auth config guide](/docs/authentication/programmatic-auth-configs).
## Why does the OAuth consent screen show "Composio" instead of my app?
-By default, the consent screen uses Composio's OAuth app. To show your own app name and logo, create your own OAuth app and set a custom redirect URL. See [White-labeling authentication](/docs/white-labeling-authentication#using-your-own-oauth-apps).
+By default, the consent screen uses Composio's OAuth app. To show your own app name and logo, create your own OAuth app and set a custom redirect URL. See [White-labeling authentication](/docs/authentication/white-labeling-authentication#using-your-own-oauth-apps).
## Why am I getting 401 errors on tool calls?
diff --git a/docs/content/toolkits/faq/googledrive.md b/docs/content/toolkits/faq/googledrive.md
index cdee520cf..6e1ac2a19 100644
--- a/docs/content/toolkits/faq/googledrive.md
+++ b/docs/content/toolkits/faq/googledrive.md
@@ -14,11 +14,11 @@ When using custom OAuth credentials, the Google Drive API must be enabled in the
## Why am I getting "Error 400: invalid_scope"?
-The requested scopes are invalid or incorrectly formatted in the authorization URL. Verify your scope values against the [Google OAuth scopes docs](https://developers.google.com/identity/protocols/oauth2). If you're creating auth configs programmatically, see the [programmatic auth config guide](/docs/programmatic-auth-configs).
+The requested scopes are invalid or incorrectly formatted in the authorization URL. Verify your scope values against the [Google OAuth scopes docs](https://developers.google.com/identity/protocols/oauth2). If you're creating auth configs programmatically, see the [programmatic auth config guide](/docs/authentication/programmatic-auth-configs).
## Why does the OAuth consent screen show "Composio" instead of my app?
-By default, the consent screen uses Composio's OAuth app. To show your own app name and logo, create your own OAuth app and set a custom redirect URL. See [White-labeling authentication](/docs/white-labeling-authentication#using-your-own-oauth-apps).
+By default, the consent screen uses Composio's OAuth app. To show your own app name and logo, create your own OAuth app and set a custom redirect URL. See [White-labeling authentication](/docs/authentication/white-labeling-authentication#using-your-own-oauth-apps).
## Why am I getting 401 errors on tool calls?
diff --git a/docs/content/toolkits/faq/googlemeet.md b/docs/content/toolkits/faq/googlemeet.md
index e28a717a3..375776069 100644
--- a/docs/content/toolkits/faq/googlemeet.md
+++ b/docs/content/toolkits/faq/googlemeet.md
@@ -14,11 +14,11 @@ When using custom OAuth credentials, the Google Meet API must be enabled in the
## Why am I getting "Error 400: invalid_scope"?
-The requested scopes are invalid or incorrectly formatted in the authorization URL. Verify your scope values against the [Google OAuth scopes docs](https://developers.google.com/identity/protocols/oauth2). If you're creating auth configs programmatically, see the [programmatic auth config guide](/docs/programmatic-auth-configs).
+The requested scopes are invalid or incorrectly formatted in the authorization URL. Verify your scope values against the [Google OAuth scopes docs](https://developers.google.com/identity/protocols/oauth2). If you're creating auth configs programmatically, see the [programmatic auth config guide](/docs/authentication/programmatic-auth-configs).
## Why does the OAuth consent screen show "Composio" instead of my app?
-By default, the consent screen uses Composio's OAuth app. To show your own app name and logo, create your own OAuth app and set a custom redirect URL. See [White-labeling authentication](/docs/white-labeling-authentication#using-your-own-oauth-apps).
+By default, the consent screen uses Composio's OAuth app. To show your own app name and logo, create your own OAuth app and set a custom redirect URL. See [White-labeling authentication](/docs/authentication/white-labeling-authentication#using-your-own-oauth-apps).
## Why am I getting 401 errors on tool calls?
diff --git a/docs/content/toolkits/faq/googlesheets.md b/docs/content/toolkits/faq/googlesheets.md
index a42261a87..3493e3a26 100644
--- a/docs/content/toolkits/faq/googlesheets.md
+++ b/docs/content/toolkits/faq/googlesheets.md
@@ -14,11 +14,11 @@ When using custom OAuth credentials, the Google Sheets API must be enabled in th
## Why am I getting "Error 400: invalid_scope"?
-The requested scopes are invalid or incorrectly formatted in the authorization URL. Verify your scope values against the [Google OAuth scopes docs](https://developers.google.com/identity/protocols/oauth2). If you're creating auth configs programmatically, see the [programmatic auth config guide](/docs/programmatic-auth-configs).
+The requested scopes are invalid or incorrectly formatted in the authorization URL. Verify your scope values against the [Google OAuth scopes docs](https://developers.google.com/identity/protocols/oauth2). If you're creating auth configs programmatically, see the [programmatic auth config guide](/docs/authentication/programmatic-auth-configs).
## Why does the OAuth consent screen show "Composio" instead of my app?
-By default, the consent screen uses Composio's OAuth app. To show your own app name and logo, create your own OAuth app and set a custom redirect URL. See [White-labeling authentication](/docs/white-labeling-authentication#using-your-own-oauth-apps).
+By default, the consent screen uses Composio's OAuth app. To show your own app name and logo, create your own OAuth app and set a custom redirect URL. See [White-labeling authentication](/docs/authentication/white-labeling-authentication#using-your-own-oauth-apps).
## Why am I getting 401 errors on tool calls?
diff --git a/docs/content/toolkits/faq/googleslides.md b/docs/content/toolkits/faq/googleslides.md
index bc214da42..4fd1f1d01 100644
--- a/docs/content/toolkits/faq/googleslides.md
+++ b/docs/content/toolkits/faq/googleslides.md
@@ -14,11 +14,11 @@ When using custom OAuth credentials, the Google Slides API must be enabled in th
## Why am I getting "Error 400: invalid_scope"?
-The requested scopes are invalid or incorrectly formatted in the authorization URL. Verify your scope values against the [Google OAuth scopes docs](https://developers.google.com/identity/protocols/oauth2). If you're creating auth configs programmatically, see the [programmatic auth config guide](/docs/programmatic-auth-configs).
+The requested scopes are invalid or incorrectly formatted in the authorization URL. Verify your scope values against the [Google OAuth scopes docs](https://developers.google.com/identity/protocols/oauth2). If you're creating auth configs programmatically, see the [programmatic auth config guide](/docs/authentication/programmatic-auth-configs).
## Why does the OAuth consent screen show "Composio" instead of my app?
-By default, the consent screen uses Composio's OAuth app. To show your own app name and logo, create your own OAuth app and set a custom redirect URL. See [White-labeling authentication](/docs/white-labeling-authentication#using-your-own-oauth-apps).
+By default, the consent screen uses Composio's OAuth app. To show your own app name and logo, create your own OAuth app and set a custom redirect URL. See [White-labeling authentication](/docs/authentication/white-labeling-authentication#using-your-own-oauth-apps).
## Why am I getting 401 errors on tool calls?
diff --git a/docs/content/toolkits/faq/googlesuper.md b/docs/content/toolkits/faq/googlesuper.md
index c4b66f205..755aecbde 100644
--- a/docs/content/toolkits/faq/googlesuper.md
+++ b/docs/content/toolkits/faq/googlesuper.md
@@ -14,8 +14,8 @@ When using custom OAuth credentials, the required Google API must be enabled in
## Why am I getting "Error 400: invalid_scope"?
-The requested scopes are invalid or incorrectly formatted in the authorization URL. Verify your scope values against the [Google OAuth scopes docs](https://developers.google.com/identity/protocols/oauth2). If you're creating auth configs programmatically, see the [programmatic auth config guide](/docs/programmatic-auth-configs).
+The requested scopes are invalid or incorrectly formatted in the authorization URL. Verify your scope values against the [Google OAuth scopes docs](https://developers.google.com/identity/protocols/oauth2). If you're creating auth configs programmatically, see the [programmatic auth config guide](/docs/authentication/programmatic-auth-configs).
## Why does the OAuth consent screen show "Composio" instead of my app?
-By default, the consent screen uses Composio's OAuth app. To show your own app name and logo, create your own OAuth app and set a custom redirect URL. See [White-labeling authentication](/docs/white-labeling-authentication#using-your-own-oauth-apps).
+By default, the consent screen uses Composio's OAuth app. To show your own app name and logo, create your own OAuth app and set a custom redirect URL. See [White-labeling authentication](/docs/authentication/white-labeling-authentication#using-your-own-oauth-apps).
diff --git a/docs/content/toolkits/faq/googletasks.md b/docs/content/toolkits/faq/googletasks.md
index 3a4eb3c1d..1a9429575 100644
--- a/docs/content/toolkits/faq/googletasks.md
+++ b/docs/content/toolkits/faq/googletasks.md
@@ -14,11 +14,11 @@ When using custom OAuth credentials, the Google Tasks API must be enabled in the
## Why am I getting "Error 400: invalid_scope"?
-The requested scopes are invalid or incorrectly formatted in the authorization URL. Verify your scope values against the [Google OAuth scopes docs](https://developers.google.com/identity/protocols/oauth2). If you're creating auth configs programmatically, see the [programmatic auth config guide](/docs/programmatic-auth-configs).
+The requested scopes are invalid or incorrectly formatted in the authorization URL. Verify your scope values against the [Google OAuth scopes docs](https://developers.google.com/identity/protocols/oauth2). If you're creating auth configs programmatically, see the [programmatic auth config guide](/docs/authentication/programmatic-auth-configs).
## Why does the OAuth consent screen show "Composio" instead of my app?
-By default, the consent screen uses Composio's OAuth app. To show your own app name and logo, create your own OAuth app and set a custom redirect URL. See [White-labeling authentication](/docs/white-labeling-authentication#using-your-own-oauth-apps).
+By default, the consent screen uses Composio's OAuth app. To show your own app name and logo, create your own OAuth app and set a custom redirect URL. See [White-labeling authentication](/docs/authentication/white-labeling-authentication#using-your-own-oauth-apps).
## Why am I getting 401 errors on tool calls?
diff --git a/docs/content/toolkits/managed-auth.mdx b/docs/content/toolkits/managed-auth.mdx
index 80b46feb5..7a5bbc113 100644
--- a/docs/content/toolkits/managed-auth.mdx
+++ b/docs/content/toolkits/managed-auth.mdx
@@ -41,7 +41,7 @@ You need a custom auth config when you want to:
- **Request specific scopes** beyond Composio's defaults.
- **Use a toolkit without managed auth**, where you supply an API key, bearer token, or instance details.
-See [Managed vs custom auth](/docs/custom-app-vs-managed-app) for the full decision guide and setup steps. You can mix the two: use your own credentials for some toolkits and managed auth for the rest.
+See [Managed vs custom auth](/docs/authentication/custom-app-vs-managed-app) for the full decision guide and setup steps. You can mix the two: use your own credentials for some toolkits and managed auth for the rest.
## Find a toolkit
diff --git a/docs/lib/standup-bot-source.json b/docs/lib/standup-bot-source.json
index 43939637a..2b223a69d 100644
--- a/docs/lib/standup-bot-source.json
+++ b/docs/lib/standup-bot-source.json
@@ -46,7 +46,7 @@
},
{
"path": "scripts/setup.ts",
- "contents": "import { Composio } from \"@composio/core\";\nimport { env } from \"../api/_utils/env\";\n\n// One-time setup: connect the bot's Slack (\"slackbot\") account so it can post to\n// the channel and DM members. Run with `npx tsx scripts/setup.ts`, or\n// `--reconnect` to clear and re-do the OAuth (needed after changing Slack scopes).\nconst COMPOSIO_BASE_URL = \"https://backend.composio.dev\";\nconst TOOLKIT_SLUG = \"slackbot\";\n\n// Scopes the bot's OAuth *user* token must carry. Composio freezes the scopes at\n// connect time, so we check them before connecting and tell the user what to add.\nconst REQUIRED_USER_SCOPES = [\"team:read\"];\n\nconst log = {\n ok: (msg: string) => console.log(` ✅ ${msg}`),\n info: (msg: string) => console.log(` · ${msg}`),\n warn: (msg: string) => console.log(` ⚠️ ${msg}`),\n};\n\nfunction errMessage(err: unknown): string {\n if (err && typeof err === \"object\") {\n const e = err as {\n error?: { error?: { message?: string }; message?: string };\n message?: string;\n };\n return e.error?.error?.message ?? e.error?.message ?? e.message ?? String(err);\n }\n return String(err);\n}\n\nasync function main() {\n const RECONNECT = process.argv.includes(\"--reconnect\");\n\n console.log(\"\\n╭─────────────────────────────────────────────────────────╮\");\n console.log(\"│ Daily Standup Bot: One-Time Setup │\");\n console.log(\"╰─────────────────────────────────────────────────────────╯\");\n if (RECONNECT) {\n console.log(\" (--reconnect: will clear and re-do the bot's Slack auth)\");\n }\n\n const composio = new Composio({ apiKey: env.COMPOSIO_API_KEY });\n const authConfigId = env.COMPOSIO_SLACKBOT_AUTH_CONFIG_ID;\n\n // Check the auth config requests the scopes the bot needs.\n // READ-ONLY on purpose. GET returns secrets MASKED, and a PATCH that echoes\n // those masked values back overwrites the real client_secret with the mask.\n // So we never write credentials here; we only check and warn.\n const cfgRes = await fetch(`${COMPOSIO_BASE_URL}/api/v3/auth_configs/${authConfigId}`, {\n headers: { \"x-api-key\": env.COMPOSIO_API_KEY },\n });\n if (cfgRes.ok) {\n const cfg = (await cfgRes.json().catch(() => ({}))) as {\n credentials?: { user_scopes?: string[] };\n };\n const userScopes = cfg.credentials?.user_scopes ?? [];\n const missing = REQUIRED_USER_SCOPES.filter((s) => !userScopes.includes(s));\n if (missing.length > 0) {\n log.warn(`Auth config is missing required user scope(s): ${missing.join(\", \")}`);\n console.log(\n \" Add them under the auth config's User Token Scopes in the Composio\\n\" +\n \" dashboard (Auth Configs → slackbot), then re-run with --reconnect.\"\n );\n } else {\n log.ok(\"Auth config has the required user scopes.\");\n }\n }\n\n // Ensure the bot's Slack connection is active.\n const session = await composio.create(\"default\", {\n authConfigs: { slackbot: authConfigId },\n });\n\n async function listSlackbotAccounts() {\n try {\n const res = await composio.connectedAccounts.list({\n userIds: [\"default\"],\n toolkitSlugs: [TOOLKIT_SLUG],\n });\n return res.items;\n } catch {\n return [];\n }\n }\n\n if (RECONNECT) {\n const accounts = await listSlackbotAccounts();\n if (accounts.length === 0) {\n log.info(\"No existing connections to clear.\");\n } else {\n for (const acc of accounts) {\n try {\n await composio.connectedAccounts.delete(acc.id);\n log.ok(`Removed old connection ${acc.id}.`);\n } catch (err) {\n log.warn(`Could not remove ${acc.id}: ${errMessage(err)}`);\n }\n }\n }\n }\n\n let connected = false;\n if (!RECONNECT) {\n const toolkits = await session.toolkits({ toolkits: [TOOLKIT_SLUG] });\n connected = !!toolkits.items.find((t) => t.slug === TOOLKIT_SLUG)?.connection\n ?.isActive;\n }\n\n if (connected) {\n log.ok(\"Bot is already connected to Slack.\");\n } else {\n log.info(\"Bot is not connected yet. Generating an authorization link…\");\n // Manual authentication: authorize() returns a Connect Link, then\n // waitForConnection() resolves once the bot finishes OAuth in the browser.\n // https://docs.composio.dev/docs/manually-authenticating\n const connectionRequest = await session.authorize(TOOLKIT_SLUG);\n if (!connectionRequest.redirectUrl) {\n throw new Error(\"Composio did not return an authorization link.\");\n }\n\n console.log(\"\\n Open this URL in your browser to authorize the bot:\\n\");\n console.log(` ${connectionRequest.redirectUrl}\\n`);\n console.log(\" Waiting for you to complete the OAuth flow (Ctrl+C to abort)…\");\n\n const TIMEOUT_MS = 5 * 60 * 1000;\n const account = await connectionRequest.waitForConnection(TIMEOUT_MS);\n log.ok(`Bot connected to Slack (${account.id}).`);\n }\n\n console.log(`\\n${\"─\".repeat(70)}`);\n console.log(\" 🎉 Setup complete. Invite the bot to your standup channel and\");\n console.log(\" point your Slack app's Interactivity Request URL at\");\n console.log(\" https://<your-deployment>/api/interactivity\");\n console.log(`${\"─\".repeat(70)}\\n`);\n}\n\nmain().catch((err) => {\n console.error(`\\n ❌ ${errMessage(err)}\\n`);\n process.exit(1);\n});\n",
+ "contents": "import { Composio } from \"@composio/core\";\nimport { env } from \"../api/_utils/env\";\n\n// One-time setup: connect the bot's Slack (\"slackbot\") account so it can post to\n// the channel and DM members. Run with `npx tsx scripts/setup.ts`, or\n// `--reconnect` to clear and re-do the OAuth (needed after changing Slack scopes).\nconst COMPOSIO_BASE_URL = \"https://backend.composio.dev\";\nconst TOOLKIT_SLUG = \"slackbot\";\n\n// Scopes the bot's OAuth *user* token must carry. Composio freezes the scopes at\n// connect time, so we check them before connecting and tell the user what to add.\nconst REQUIRED_USER_SCOPES = [\"team:read\"];\n\nconst log = {\n ok: (msg: string) => console.log(` ✅ ${msg}`),\n info: (msg: string) => console.log(` · ${msg}`),\n warn: (msg: string) => console.log(` ⚠️ ${msg}`),\n};\n\nfunction errMessage(err: unknown): string {\n if (err && typeof err === \"object\") {\n const e = err as {\n error?: { error?: { message?: string }; message?: string };\n message?: string;\n };\n return e.error?.error?.message ?? e.error?.message ?? e.message ?? String(err);\n }\n return String(err);\n}\n\nasync function main() {\n const RECONNECT = process.argv.includes(\"--reconnect\");\n\n console.log(\"\\n╭─────────────────────────────────────────────────────────╮\");\n console.log(\"│ Daily Standup Bot: One-Time Setup │\");\n console.log(\"╰─────────────────────────────────────────────────────────╯\");\n if (RECONNECT) {\n console.log(\" (--reconnect: will clear and re-do the bot's Slack auth)\");\n }\n\n const composio = new Composio({ apiKey: env.COMPOSIO_API_KEY });\n const authConfigId = env.COMPOSIO_SLACKBOT_AUTH_CONFIG_ID;\n\n // Check the auth config requests the scopes the bot needs.\n // READ-ONLY on purpose. GET returns secrets MASKED, and a PATCH that echoes\n // those masked values back overwrites the real client_secret with the mask.\n // So we never write credentials here; we only check and warn.\n const cfgRes = await fetch(`${COMPOSIO_BASE_URL}/api/v3/auth_configs/${authConfigId}`, {\n headers: { \"x-api-key\": env.COMPOSIO_API_KEY },\n });\n if (cfgRes.ok) {\n const cfg = (await cfgRes.json().catch(() => ({}))) as {\n credentials?: { user_scopes?: string[] };\n };\n const userScopes = cfg.credentials?.user_scopes ?? [];\n const missing = REQUIRED_USER_SCOPES.filter((s) => !userScopes.includes(s));\n if (missing.length > 0) {\n log.warn(`Auth config is missing required user scope(s): ${missing.join(\", \")}`);\n console.log(\n \" Add them under the auth config's User Token Scopes in the Composio\\n\" +\n \" dashboard (Auth Configs → slackbot), then re-run with --reconnect.\"\n );\n } else {\n log.ok(\"Auth config has the required user scopes.\");\n }\n }\n\n // Ensure the bot's Slack connection is active.\n const session = await composio.create(\"default\", {\n authConfigs: { slackbot: authConfigId },\n });\n\n async function listSlackbotAccounts() {\n try {\n const res = await composio.connectedAccounts.list({\n userIds: [\"default\"],\n toolkitSlugs: [TOOLKIT_SLUG],\n });\n return res.items;\n } catch {\n return [];\n }\n }\n\n if (RECONNECT) {\n const accounts = await listSlackbotAccounts();\n if (accounts.length === 0) {\n log.info(\"No existing connections to clear.\");\n } else {\n for (const acc of accounts) {\n try {\n await composio.connectedAccounts.delete(acc.id);\n log.ok(`Removed old connection ${acc.id}.`);\n } catch (err) {\n log.warn(`Could not remove ${acc.id}: ${errMessage(err)}`);\n }\n }\n }\n }\n\n let connected = false;\n if (!RECONNECT) {\n const toolkits = await session.toolkits({ toolkits: [TOOLKIT_SLUG] });\n connected = !!toolkits.items.find((t) => t.slug === TOOLKIT_SLUG)?.connection\n ?.isActive;\n }\n\n if (connected) {\n log.ok(\"Bot is already connected to Slack.\");\n } else {\n log.info(\"Bot is not connected yet. Generating an authorization link…\");\n // Manual authentication: authorize() returns a Connect Link, then\n // waitForConnection() resolves once the bot finishes OAuth in the browser.\n // https://docs.composio.dev/docs/authentication/manually-authenticating\n const connectionRequest = await session.authorize(TOOLKIT_SLUG);\n if (!connectionRequest.redirectUrl) {\n throw new Error(\"Composio did not return an authorization link.\");\n }\n\n console.log(\"\\n Open this URL in your browser to authorize the bot:\\n\");\n console.log(` ${connectionRequest.redirectUrl}\\n`);\n console.log(\" Waiting for you to complete the OAuth flow (Ctrl+C to abort)…\");\n\n const TIMEOUT_MS = 5 * 60 * 1000;\n const account = await connectionRequest.waitForConnection(TIMEOUT_MS);\n log.ok(`Bot connected to Slack (${account.id}).`);\n }\n\n console.log(`\\n${\"─\".repeat(70)}`);\n console.log(\" 🎉 Setup complete. Invite the bot to your standup channel and\");\n console.log(\" point your Slack app's Interactivity Request URL at\");\n console.log(\" https://<your-deployment>/api/interactivity\");\n console.log(`${\"─\".repeat(70)}\\n`);\n}\n\nmain().catch((err) => {\n console.error(`\\n ❌ ${errMessage(err)}\\n`);\n process.exit(1);\n});\n",
"composio": true
}
]
diff --git a/docs/next.config.mjs b/docs/next.config.mjs
index c4e0d056a..c5fbd0b3c 100644
--- a/docs/next.config.mjs
+++ b/docs/next.config.mjs
@@ -298,27 +298,27 @@ const config = {
},
{
source: '/tool-router/manually-authenticating-users',
- destination: '/docs/manually-authenticating',
+ destination: '/docs/authentication/manually-authenticating',
permanent: true,
},
{
source: '/tool-router/using-custom-auth-configs',
- destination: '/docs/custom-app-vs-managed-app',
+ destination: '/docs/authentication/custom-app-vs-managed-app',
permanent: true,
},
{
source: '/docs/authenticating-users/using-custom-auth-configs',
- destination: '/docs/custom-app-vs-managed-app',
+ destination: '/docs/authentication/custom-app-vs-managed-app',
permanent: true,
},
{
source: '/tool-router/white-labeling-authentication',
- destination: '/docs/white-labeling-authentication',
+ destination: '/docs/authentication/white-labeling-authentication',
permanent: true,
},
{
source: '/tool-router/managing-multiple-accounts',
- destination: '/docs/managing-multiple-connected-accounts',
+ destination: '/docs/authentication/managing-multiple-connected-accounts',
permanent: true,
},
// Provider redirects (old fern URLs -> new docs URLs)
@@ -439,23 +439,65 @@ const config = {
// Programmatic auth configs consolidated into the Customizing auth section
{
source: '/docs/auth-configuration/programmatic-auth-configs',
- destination: '/docs/programmatic-auth-configs',
+ destination: '/docs/authentication/programmatic-auth-configs',
permanent: true,
},
// Authenticating users folder flattened into the Authenticate users section
{
source: '/docs/authenticating-users/manually-authenticating',
- destination: '/docs/manually-authenticating',
+ destination: '/docs/authentication/manually-authenticating',
permanent: true,
},
{
source: '/docs/authenticating-users/managing-multiple-connected-accounts',
- destination: '/docs/managing-multiple-connected-accounts',
+ destination: '/docs/authentication/managing-multiple-connected-accounts',
permanent: true,
},
{
source: '/docs/authenticating-users/shared-connections',
- destination: '/docs/shared-connections',
+ destination: '/docs/extending-sessions/shared-connections',
+ permanent: true,
+ },
+ // Auth guides regrouped under the Authentication folder; shared connections
+ // moved to Extend sessions. These sources carry 36-42% Google entry traffic.
+ {
+ source: '/docs/manually-authenticating',
+ destination: '/docs/authentication/manually-authenticating',
+ permanent: true,
+ },
+ {
+ source: '/docs/managing-multiple-connected-accounts',
+ destination: '/docs/authentication/managing-multiple-connected-accounts',
+ permanent: true,
+ },
+ {
+ source: '/docs/importing-existing-connections',
+ destination: '/docs/authentication/importing-existing-connections',
+ permanent: true,
+ },
+ {
+ source: '/docs/custom-app-vs-managed-app',
+ destination: '/docs/authentication/custom-app-vs-managed-app',
+ permanent: true,
+ },
+ {
+ source: '/docs/programmatic-auth-configs',
+ destination: '/docs/authentication/programmatic-auth-configs',
+ permanent: true,
+ },
+ {
+ source: '/docs/controlling-scopes',
+ destination: '/docs/authentication/controlling-scopes',
+ permanent: true,
+ },
+ {
+ source: '/docs/white-labeling-authentication',
+ destination: '/docs/authentication/white-labeling-authentication',
+ permanent: true,
+ },
+ {
+ source: '/docs/shared-connections',
+ destination: '/docs/extending-sessions/shared-connections',
permanent: true,
},
// Authentication reference renamed to "Authenticating to Composio"
@@ -948,22 +990,22 @@ const config = {
},
{
source: '/docs/guides/managing-multiple-connected-accounts',
- destination: '/docs/managing-multiple-connected-accounts',
+ destination: '/docs/authentication/managing-multiple-connected-accounts',
permanent: true,
},
{
source: '/docs/guides/white-labeling-authentication',
- destination: '/docs/white-labeling-authentication',
+ destination: '/docs/authentication/white-labeling-authentication',
permanent: true,
},
{
source: '/docs/using-custom-auth-configuration',
- destination: '/docs/custom-app-vs-managed-app',
+ destination: '/docs/authentication/custom-app-vs-managed-app',
permanent: true,
},
{
source: '/docs/guides/using-custom-auth-configuration',
- destination: '/docs/custom-app-vs-managed-app',
+ destination: '/docs/authentication/custom-app-vs-managed-app',
permanent: true,
},
{
@@ -1047,7 +1089,7 @@ const config = {
// Legacy /docs/white-labeling → sessions white-labeling page
{
source: '/docs/white-labeling',
- destination: '/docs/white-labeling-authentication',
+ destination: '/docs/authentication/white-labeling-authentication',
permanent: true,
},
];
diff --git a/docs/tests/integration/redirects.test.ts b/docs/tests/integration/redirects.test.ts
index 767e10723..5670ab0c2 100644
--- a/docs/tests/integration/redirects.test.ts
+++ b/docs/tests/integration/redirects.test.ts
@@ -37,6 +37,9 @@ const REDIRECTS = [
{ from: "/docs/sandbox", to: "/docs/sandbox/remote" },
{ from: "/docs/custom-tools-and-toolkits", to: "/docs/extending-sessions/custom-tools-and-toolkits" },
{ from: "/docs/proxy-execute", to: "/docs/extending-sessions/proxy-execute" },
+ { from: "/docs/white-labeling-authentication", to: "/docs/authentication/white-labeling-authentication" },
+ { from: "/docs/shared-connections", to: "/docs/extending-sessions/shared-connections" },
+ { from: "/docs/manually-authenticating", to: "/docs/authentication/manually-authenticating" },
];
describe("Redirects - key patterns", () => {
diff --git a/docs/tests/static/navigation.test.ts b/docs/tests/static/navigation.test.ts
index 21593305c..0aa3b16d6 100644
--- a/docs/tests/static/navigation.test.ts
+++ b/docs/tests/static/navigation.test.ts
@@ -53,7 +53,8 @@ describe("Navigation - meta.json validity", () => {
"---Core concepts---",
"---Guides---",
"---Direct execution (legacy)---",
- "---Migration and security---",
+ "---Migration---",
+ "---Security and data---",
]);
expect(pages.slice(1, pages.indexOf("---Core concepts---"))).toEqual([
@@ -68,7 +69,7 @@ describe("Navigation - meta.json validity", () => {
expect(
pages.slice(
pages.indexOf("---Direct execution (legacy)---") + 1,
- pages.indexOf("---Migration and security---")
+ pages.indexOf("---Migration---")
)
).toEqual([
"sessions-vs-direct-execution",
diff --git a/docs/tests/static/start-routing.test.ts b/docs/tests/static/start-routing.test.ts
index e9edf3389..e113a8fcd 100644
--- a/docs/tests/static/start-routing.test.ts
+++ b/docs/tests/static/start-routing.test.ts
@@ -32,25 +32,30 @@ describe('getting-started routing policy', () => {
]);
});
- test('keeps progressive authentication guides in the human and agent indexes', async () => {
- const [authentication, llmsRoute] = await Promise.all([
- read('content/docs/authentication.mdx'),
- read('app/llms.txt/route.ts'),
+ test('keeps progressive authentication guides in the human hub and the sidebar', async () => {
+ const [authentication, authMeta, sessionsMeta] = await Promise.all([
+ read('content/docs/authentication/index.mdx'),
+ read('content/docs/authentication/meta.json'),
+ read('content/docs/extending-sessions/meta.json'),
]);
- const guides = [
+ const authGuides = [
'manually-authenticating',
'managing-multiple-connected-accounts',
- 'shared-connections',
'importing-existing-connections',
'custom-app-vs-managed-app',
'programmatic-auth-configs',
'controlling-scopes',
'white-labeling-authentication',
];
+ const authPages = JSON.parse(authMeta).pages as string[];
+ const sessionPages = JSON.parse(sessionsMeta).pages as string[];
- for (const guide of guides) {
- expect(authentication).toContain(`href="/docs/${guide}"`);
- expect(llmsRoute).toContain(`'/docs/${guide}'`);
+ for (const guide of authGuides) {
+ expect(authentication).toContain(`href="/docs/authentication/${guide}"`);
+ expect(authPages).toContain(guide);
}
+
+ expect(authentication).toContain('href="/docs/extending-sessions/shared-connections"');
+ expect(sessionPages).toContain('shared-connections');
});
});