Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
fix(docs): use StepTitle to keep step titles out of TOC
Replace ### headings inside <Step> with <StepTitle> across all docs pages. Markdown headings inside steps were leaking into the table of contents. StepTitle renders visually the same but is excluded from TOC. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Sushmithamallesh committed
Feb 11, 2026 at 13:49 UTC
9a026c76e497dc7c51c8e91d06b43a99f21f5354
5 files changed
+21
-21
docs/content/docs/auth-configuration/custom-auth-configs.mdx
+6
-6
@@ -41,7 +41,7 @@ However, getting OAuth approvals takes time, so Composio provides a default deve
41
42
<Steps>
43
<Step>
44
-### Generate the OAuth Client ID and Client Secret
44
+<StepTitle>Generate the OAuth Client ID and Client Secret</StepTitle>
45
46
To set up a custom OAuth config, you'll need the OAuth Client ID and Client Secret.
47
@@ -60,7 +60,7 @@ Examples for Google and GitHub:
60
</Step>
61
62
<Step>
63
-### Set the Authorized Redirect URI
63
+<StepTitle>Set the Authorized Redirect URI</StepTitle>
64
65
When creating your OAuth app, make sure to configure the Authorized Redirect URI to point to the Composio callback URL below:
66
@@ -70,7 +70,7 @@ https://backend.composio.dev/api/v3/toolkits/auth/callback
70
</Step>
71
72
<Step>
73
-### Create the auth config
73
+<StepTitle>Create the auth config</StepTitle>
74
75
Once you have the OAuth credentials, you can add them to the auth config in the dashboard.
76
@@ -131,7 +131,7 @@ To remediate this:
131
132
<Steps>
133
<Step>
134
-### Set the Authorized Redirect URI
134
+<StepTitle>Set the Authorized Redirect URI</StepTitle>
135
136
Specify the Authorized Redirect URI to your own domain in the OAuth configuration.
137
For example:
@@ -141,7 +141,7 @@ https://yourdomain.com/api/composio-redirect
141
</Step>
142
143
<Step>
144
-### Create a redirect logic
144
+<StepTitle>Create a redirect logic</StepTitle>
145
146
Create a redirect logic, either through your DNS or in your application to redirect that endpoint to `https://backend.composio.dev/api/v3/toolkits/auth/callback`
147
@@ -204,7 +204,7 @@ export default function handler(req: NextApiRequest, res: NextApiResponse) {
204
</Step>
205
206
<Step>
207
-### Create the auth config
207
+<StepTitle>Create the auth config</StepTitle>
208
209
Specify your custom redirect URI in the auth config settings!
210
docs/content/docs/migration-guide/tool-router-beta.mdx
+4
-4
@@ -10,7 +10,7 @@ The stable version includes improved session management, multiple configuring op
10
11
<Steps>
12
<Step>
13
-### Upgrade composio package
13
+<StepTitle>Upgrade composio package</StepTitle>
14
15
Upgrade to the latest stable version:
16
@@ -29,7 +29,7 @@ npm install @composio/core@latest
29
</Step>
30
31
<Step>
32
-### Update session creation
32
+<StepTitle>Update session creation</StepTitle>
33
34
<Tabs groupId="language" items={['Python', 'TypeScript']} persist>
35
<Tab value="Python">
@@ -59,7 +59,7 @@ const session = await composio.create('user_123');
59
</Step>
60
61
<Step>
62
-### Moving users (optional)
62
+<StepTitle>Moving users (optional)</StepTitle>
63
64
If you have existing users on tool router and you don't want them to authenticate again:
65
- Tool Router will auto-detect auth configs and connected accounts it created (from the beta version).
@@ -99,7 +99,7 @@ const session = await composio.create('user_123',
99
</Step>
100
101
<Step>
102
-### Explore new capabilities
102
+<StepTitle>Explore new capabilities</StepTitle>
103
104
Check out these new features available in the stable version:
105
docs/content/docs/tools-direct/authenticating-tools.mdx
+5
-5
@@ -18,19 +18,19 @@ An **Auth Config** is a blueprint that defines how authentication works for a to
18
19
<Steps>
20
<Step>
21
-### Selecting a toolkit
21
+<StepTitle>Selecting a toolkit</StepTitle>
22
23
Navigate to [Auth Configs](https://platform.composio.dev?next_page=%2Fauth-configs) tab in your dashboard and click "**Create Auth Config**". Find and select the toolkit you want to integrate (e.g., **Gmail**, **Slack**, **GitHub**).
24
</Step>
25
26
<Step>
27
-### Selecting the Authentication method
27
+<StepTitle>Selecting the Authentication method</StepTitle>
28
29
Each toolkit supports different authentication methods such as **OAuth**, **API Key**, **Bearer Token**. Select from the available options for your toolkit.
30
</Step>
31
32
<Step>
33
-### Configure scopes
33
+<StepTitle>Configure scopes</StepTitle>
34
35
Depending on your authentication method, you may need to configure scopes:
36
- **OAuth2**: Configure scopes for what data and actions your app can access.
@@ -38,7 +38,7 @@ Depending on your authentication method, you may need to configure scopes:
38
</Step>
39
40
<Step>
41
-### Authentication Management
41
+<StepTitle>Authentication Management</StepTitle>
42
43
**For OAuth toolkits:**
44
- **Development/Testing**: Use Composio's managed authentication (no setup required)
@@ -54,7 +54,7 @@ Want to remove Composio branding from OAuth screens? See [Custom Auth Configs](/
54
</Step>
55
56
<Step>
57
-### You are all set!
57
+<StepTitle>You are all set!</StepTitle>
58
59
Click "**Create Auth Configuration**" button and you have completed your first step! Now you can move ahead to authenticating your users by [Connecting an Account](#connecting-an-account).
60
</Step>
docs/content/docs/using-custom-auth-configuration.mdx
+3
-3
@@ -8,13 +8,13 @@ Some toolkits don't have Composio managed authentication and require you to prov
8
9
<Steps>
10
<Step>
11
-### Check if a toolkit needs custom credentials
11
+<StepTitle>Check if a toolkit needs custom credentials</StepTitle>
12
13
In the [Composio platform](https://platform.composio.dev), go to "All Toolkits" and select the toolkit. If it shows no Composio managed auth schemes, you'll need to create an auth config.
14
</Step>
15
16
<Step>
17
-### Create an auth config
17
+<StepTitle>Create an auth config</StepTitle>
18
19
1. Go to **Authentication management** in the [dashboard](https://platform.composio.dev)
20
2. Click **Create Auth Config**
@@ -31,7 +31,7 @@ For detailed instructions on getting credentials for specific toolkits, see [Cus
31
</Step>
32
33
<Step>
34
-### Use in your session
34
+<StepTitle>Use in your session</StepTitle>
35
36
Pass your auth config ID when creating a session:
37
docs/content/docs/white-labeling-authentication.mdx
+3
-3
@@ -10,7 +10,7 @@ By default, OAuth screens show Composio's branding. With white-labeling, they'll
10
11
<Steps>
12
<Step>
13
-### Create an OAuth app
13
+<StepTitle>Create an OAuth app</StepTitle>
14
15
Create a developer app in the toolkit's developer portal. You'll need the client ID and client secret. Set the callback URL to:
16
@@ -24,7 +24,7 @@ For step-by-step guides on creating OAuth apps for some toolkits, see [composio.
24
</Step>
25
26
<Step>
27
-### Create auth config
27
+<StepTitle>Create auth config</StepTitle>
28
29
Create an auth config in the [Composio dashboard](https://platform.composio.dev):
30
@@ -43,7 +43,7 @@ For detailed instructions with screenshots, see [Custom auth configs](/docs/auth
43
</Step>
44
45
<Step>
46
-### Use in your session
46
+<StepTitle>Use in your session</StepTitle>
47
48
Pass your auth config ID in the session:
49