@devries-cameron20 / composio Mirror · read-only / commits / eb4a18dad
Fork 0

Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.

Mirrored from https://github.com/Camo67/composio.git

Synced Nov 21, 06:00 UTC

docs: say managed auth works in production in the auth step and agent skill

The "Authentication Management" step labeled managed auth as Development/Testing and your own OAuth credentials as Production. The agent skill said managed auth is intended to make initial development easy and to move before launch. Both read as "managed apps are for prototypes". Say that managed auth works in production, and recommend your own OAuth credentials for higher volume, dedicated rate limits and your own consent screen. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

Brendan O'Leary committed Nov 11, 2026 at 19:20 UTC eb4a18dad81a537222d54bdb7854786de10aa9bb
2 files changed +3 -3
docs/content/docs/tools-direct/authenticating-tools.mdx
+2 -2
@@ -51,8 +51,8 @@ Depending on your authentication method, you may need to configure scopes:
51 <StepTitle>Authentication Management</StepTitle>
52
53 **For OAuth toolkits:**
54 -- **Development/Testing**: Use Composio's managed authentication (no setup required)
55 -- **Production**: Generate your own OAuth credentials from the toolkit's developer portal
54 +- **Getting started**: Use Composio's managed authentication. It needs no setup and works in production.
55 +- **Higher volume or your own branding**: We recommend your own OAuth credentials from the toolkit's developer portal. They give you dedicated rate limits and your own name on the consent screen.
56
57 **For custom authentication schemes:**
58
skills/composio/references/errors.md
+1 -1
@@ -62,7 +62,7 @@ If the MCP client itself cannot authenticate, verify the consumer endpoint, OAut
62
63 ## Branding and production auth
64
65 -Managed auth is intended to make initial development easy. Before launch, move integrations that require the application's branding, scopes, or dedicated quotas onto its own OAuth apps.
65 +Managed auth works in production and is the fastest way to start. Recommend your own OAuth app when the application needs its own branding, its own scopes, or dedicated provider rate limits.
66
67 When someone asks to remove Composio branding, identify the surface first: Connect Link page, provider consent screen, secured badge, callback domain, or success page. They have different fixes. Fetch `white-labeling-authentication.md` before proposing an implementation.
68