@devries-cameron20 / composio-1 / commits / 2c528abb9
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.

docs: clarify branded OAuth flows and callback domain limits (#5021)

## Summary Address Gauge's high-priority recommendation for a branded OAuth implementation guide (action `cmtzenqao01xo0it2v52i8wb9`). Strengthen the existing canonical documentation rather than publish a duplicate guide or blog. ## Changes - Distinguish branded hosted Connect Link from app-owned connection UI using supported custom-OAuth initiation. - Document custom OAuth app setup, cURL/SDK initiation, explicit auth-config/account selection, server-side connection verification, and deployment checks. - Separate the provider's `redirect_uri` from the application's `callbackUrl`; explicitly state which domains remain visible and avoid claiming CNAME or self-hosted Connect Link support. - Correct the claim that a 302 callback forwarder hides Composio or never receives authorization codes. Update the diagram and reviewed Google OAuth KB article; leave the upstream source snapshot untouched. - Consolidate legacy direct-execution guidance into focused canonical links. ## Verification - `bun run lint:links`: passed, zero errors in both site and SDK link checks. - `bun run types:check`: passed. - `bun run lint`: completed successfully with warnings in other files; no lint-clean claim for the whole repository. - Twoslash checked all four TypeScript blocks in the canonical guide against installed dependencies: passed. - Validated both documented OAuth POST payloads against the current OpenAPI v3 schemas using Ajv: passed. - Rendered both canonical and legacy articles with the real MDX component registry and inspected them in Chromium, including the corrected callback diagram. This was a standalone article render, not the full Next.js site shell. - `generate:kb` ran through the normal build/typecheck prerequisites for the reviewed article change. ### Verification limits - Structural test invocation: 16 passed; the all-content HTML-nesting test exceeded its explicit 30-second timeout. No content assertion failure was reported, but that test did not complete. - `bun run build` timed out after 600 seconds during production compilation; no successful production build is claimed. - Full-site preview validation was unavailable: default preview navigation timed out, and Webpack fallback failed on the existing `fumadocs-mdx:collections/server` loader scheme in the companion guide worktree. No framework configuration changes are included. - No live provider OAuth flow was executed. Actual navigation, provider verification, toolkit-specific direct-initiation behavior, and consent/cancellation outcomes must be checked with configured OAuth credentials before rollout. ## Type of change - [x] Documentation ## Review notes Please review the full diff, especially toolkit-specific direct initiation and callback-domain limits. No permanent wording/source-text tests or changeset: this is documentation plus its illustrative component. Designated reviewer: @jkomyno.

Brendan O'Leary committed Oct 28, 2026 at 15:34 UTC 2c528abb9f8a79138e781d57576a0a0aa7639b36

No changes.