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 direct paths instead of relying on redirects
- Fix broken link /docs/guides/white-labeling-authentication - Update 3 other links to use direct paths instead of redirects Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Sushmithamallesh committed
Feb 2, 2026 at 19:28 UTC
2c3f505ff40c365746b206071b984e9fbc7a4e5c
4 files changed
+4
-4
docs/content/changelog/11-05-25.mdx
+1
-1
@@ -54,7 +54,7 @@ If you're using an existing project and want to adopt this security enhancement:
54
3. Update your application code to pass the appropriate identifier
55
4. Test the updated URLs in your development environment
56
57
-For more details on choosing the right user identifiers for your application, see our [User Management documentation](https://docs.composio.dev/docs/user-management).
57
+For more details on choosing the right user identifiers for your application, see our [User Management documentation](/docs/users-and-sessions).
58
59
### Questions?
60
docs/content/changelog/12-10-25.mdx
+1
-1
@@ -4,7 +4,7 @@ description: "57 toolkits now return strongly typed objects instead of generic r
4
date: "2025-12-10"
5
---
6
7
-We've updated many toolkits so their outputs are now strongly typed objects instead of a generic `response_data` blob, meaning tools like Outlook, HubSpot, Notion, etc. now return well-shaped, documented fields you can rely on directly in your code and agents. These improvements apply to the latest toolkit versions—see our [toolkit versioning docs](https://docs.composio.dev/docs/toolkit-versioning) for how versions are managed.
7
+We've updated many toolkits so their outputs are now strongly typed objects instead of a generic `response_data` blob, meaning tools like Outlook, HubSpot, Notion, etc. now return well-shaped, documented fields you can rely on directly in your code and agents. These improvements apply to the latest toolkit versions—see our [toolkit versioning docs](/docs/tools-direct/toolkit-versioning) for how versions are managed.
8
9
<Callout type="warn">
10
**Breaking Change for `latest` Version**
docs/content/docs/index.mdx
+1
-1
@@ -87,7 +87,7 @@ Composio works with any AI framework. Pick your preferred SDK:
87
<Card
88
icon={<Palette />}
89
title="White Labeling"
90
- href="/docs/guides/white-labeling-authentication"
90
+ href="/docs/white-labeling-authentication"
91
description="Customize auth screens with your branding"
92
/>
93
</Cards>
docs/content/docs/tools-direct/authenticating-tools.mdx
+1
-1
@@ -74,7 +74,7 @@ You should create multiple auth configs for the same toolkit when you need:
74
- **Different permission levels** - Limiting actions for specific use cases
75
76
<Cards>
77
- <Card title="Programmatic creation" href="/docs/programmatic-auth-configs">
77
+ <Card title="Programmatic creation" href="/docs/auth-configuration/programmatic-auth-configs">
78
For managing auth configs across multiple projects, you can create them programmatically via the API
79
</Card>
80
<Card title="Production white-labeling" href="/docs/auth-configuration/custom-auth-configs#white-labeling-the-oauth-consent-screen">