Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
TypeScript agentic-aiagentsaiai-agentsaiagentsdeveloper-toolsfunction-callinggpt-4javascriptjsllmllmopsmcppythonremote-mcp-serverssetypescript
fix(docs): Use direct paths instead of relying on redirects
Sushmithamallesh2c3f505ff40c
diff --git a/docs/content/changelog/11-05-25.mdx b/docs/content/changelog/11-05-25.mdxindex a096de723..53f65adc3 100644--- a/docs/content/changelog/11-05-25.mdx+++ b/docs/content/changelog/11-05-25.mdx@@ -54,7 +54,7 @@ If you're using an existing project and want to adopt this security enhancement:3. Update your application code to pass the appropriate identifier4. Test the updated URLs in your development environment-For more details on choosing the right user identifiers for your application, see our [User Management documentation](https://docs.composio.dev/docs/user-management).+For more details on choosing the right user identifiers for your application, see our [User Management documentation](/docs/users-and-sessions).### Questions?diff --git a/docs/content/changelog/12-10-25.mdx b/docs/content/changelog/12-10-25.mdxindex b5ac2ec9c..fe957c487 100644--- a/docs/content/changelog/12-10-25.mdx+++ b/docs/content/changelog/12-10-25.mdx@@ -4,7 +4,7 @@ description: "57 toolkits now return strongly typed objects instead of generic rdate: "2025-12-10"----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.+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.<Callout type="warn">**Breaking Change for `latest` Version**diff --git a/docs/content/docs/index.mdx b/docs/content/docs/index.mdxindex 0788c626a..ffbfb07ec 100644--- a/docs/content/docs/index.mdx+++ b/docs/content/docs/index.mdx@@ -87,7 +87,7 @@ Composio works with any AI framework. Pick your preferred SDK:<Cardicon={<Palette />}title="White Labeling"- href="/docs/guides/white-labeling-authentication"+ href="/docs/white-labeling-authentication"description="Customize auth screens with your branding"/></Cards>diff --git a/docs/content/docs/tools-direct/authenticating-tools.mdx b/docs/content/docs/tools-direct/authenticating-tools.mdxindex a0f4673e9..44180dac8 100644--- a/docs/content/docs/tools-direct/authenticating-tools.mdx+++ b/docs/content/docs/tools-direct/authenticating-tools.mdx@@ -74,7 +74,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/auth-configuration/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/custom-auth-configs#white-labeling-the-oauth-consent-screen">