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(scopes): sections for developer-side scope fixes (PLEN-4631) (#5332)
## Summary Apollo's scope-failure responses (PLEN-4629, ComposioHQ/platform#15019) give developers a `fix.url` pointing at sections of **Controlling scopes**. Two of the three targets need content: - **Set scopes with your own OAuth app** (`managed_app` failures): one lead-in sentence saying when you need your own app, namely when a tool needs a scope Composio's managed app isn't approved for. - **Tools that need a different auth scheme** (`action_not_available` failures): a new section. A tool that doesn't work under the auth config's scheme needs an auth config with a supported scheme. It links to the existing sections that show a toolkit's schemes and how to create a non-OAuth auth config. The third target, `auth_config` failures, already has its content: the callout under **Update scopes on an existing config** says existing users must reconnect. The new heading must stay as written. Its anchor `#tools-that-need-a-different-auth-scheme` is pinned in Apollo (`SCOPE_FIX_DOCS_URLS`) and ships in execute responses. Linear: [PLEN-4631](https://linear.app/composio/issue/PLEN-4631) ## Checks - `bun run lint:links` passes, including both new anchors. - No code samples were added. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
No changes.