@devries-cameron20 / composio-1 / commits / 1d651b5c8
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: remove stale DiscordBot 401 FAQ (#3888)

# Description Removes the DiscordBot FAQ entry `docs/content/toolkits/faq/discordbot.md`, which documented a "401 on the default app" caused by the Composio-managed/shared DiscordBot bot token being rejected by Discord. That managed default-app bot-token issue has since been **resolved**, so the FAQ is now stale. Leaving it up is actively misleading — it tells users the default app is broken and pushes them to create their own custom DiscordBot credentials, which is unnecessary now and has itself been a source of support confusion (e.g. Plain T-14278, where a customer went down the custom-credentials path). Scope: single content file. FAQ entries are loaded per-toolkit-slug at `content/toolkits/faq/${slug}.md`; `readToolkitFaq()` already try/catches a missing file and returns `null`, and `FaqSection`/the `llms.mdx` route both no-op when the FAQ is empty. There is no manifest/index listing `discordbot`, so removal is clean with no dangling references. # How did I test this PR - `grep -rni "401 on the default app|DiscordBot return 401|managed bot-token" docs` after deletion → **no remaining references** anywhere in the docs (content, components, prebuilt `toolkits.json`, search index). - Verified the loader tolerates the missing file: `docs/app/(home)/toolkits/[[...slug]]/page.tsx:111` `readToolkitFaq()` catches the read error → returns `null`; `FaqSection` renders nothing on empty; `docs/app/llms.mdx/[[...slug]]/route.ts:671` gates on `faqMarkdown && faqMarkdown.trim()`. So the DiscordBot toolkit page + llms.mdx simply render without a FAQ section — no build break. - Confirmed FAQ discovery is purely file-existence based (no hardcoded slug list), so no index needed updating. Co-authored-by: Zen Agent <zen@composio.dev> Co-authored-by: abhishek <abhishek@composio.dev>

composio-zen[bot] committed Jul 20, 2026 at 23:17 UTC 1d651b5c8507d5726155ad2ef7058e6eb26cc8bb
1 file changed -5
docs/content/toolkits/faq/discordbot.md deleted
-5
@@ -1,5 +0,0 @@
1 -## Why can DiscordBot return 401 on the default app?
2 -
3 -DiscordBot tool calls can return `401 {"message":"401: Unauthorized","code":0}` even when the connected account is active if the connection uses the default DiscordBot app.
4 -
5 -The default app currently has a managed bot-token issue: Discord is rejecting the shared bot token behind that app, so the connection flow can complete while bot API calls still fail. Use your own Discord app credentials in a custom DiscordBot auth config for now. Reconnect through that custom config before retrying the DiscordBot tool call.