Discord

​

Prerequisites

• A Discord account, and a server you can add the bot to (the wizard walks you through creating both the app and a server if needed)
• A working NanoClaw install (quickstart)
• A bot from the Developer Portal with Message Content Intent enabled (under Bot → Privileged Gateway Intents) — without it the bot connects but can’t read message text
• The bot token from the Bot tab. That’s the only thing you paste — the wizard derives the application ID and public key from the token via Discord’s API.

​

Install

​

Platform notes

• Gateway connection with backoff — the bridge starts a Gateway listener in 24-hour cycles and forwards raw events (including button clicks) to a local HTTP server bound to 127.0.0.1. If the listener dies, it reconnects with exponential backoff (1s doubling per consecutive failure, capped at 1 hour); a run lasting over 5 minutes counts as healthy and resets the counter. The cap exists because an unrecoverable failure like a bad token would otherwise restart ~10×/sec and get the IP blocked by Discord’s Cloudflare layer.
• Threads — the adapter sets supportsThreads: true, and on server channels the router gives every thread its own agent session automatically: even wirings set to shared behave as per-thread here. Only agent-shared (one session across all of an agent’s messaging groups) overrides this. In DMs the forcing doesn’t apply: shared wirings get a single session regardless of sub-threads, while an explicit per-thread wiring is honored — see the entity model.
• Mentions and engagement — @mentioning the bot in an unwired channel is platform-confirmed and reaches the router as a mention; in mention-sticky wirings the bot then sticks to that thread (plain mention wirings respond per mention without subscribing). DMs are always treated as addressed to the bot.
• Replies and attachments — replying to a message passes the quoted text and sender (display name or username) to the agent as context. Attachments are downloaded and passed to the agent as data, not just described.
• Interactive questions — when an agent asks a multiple-choice question, it renders as an embed with buttons; your click arrives via the Gateway and the card updates in place to show the selection.
• 2,000-character limit — Discord caps messages at 2,000 characters. The current adapter doesn’t enable the bridge’s automatic chunking, so longer replies can be truncated by the platform.
• Typing indicator — the bot shows a typing indicator while the agent works.

​

Troubleshooting

• “Discord didn’t accept that token” — /users/@me rejected it. Tokens are only shown once in the Developer Portal; click Reset Token and copy the fresh one (the old one stops working). “Couldn’t reach Discord” instead means a network problem — check connectivity and retry setup.
• Bot connects but never responds to text — Message Content Intent isn’t enabled. Developer Portal → your app → Bot → Privileged Gateway Intents → enable it, then restart the service.
• “Couldn’t open a DM channel with you” / no welcome message — the bot and your account don’t share a server yet. Open the invite URL, add the bot to any server you’re in, then retry with /manage-channels.
• Gateway listener error, retrying repeating in logs — the listener is in its backoff loop (the log line includes consecutiveFailures and the next delayMs). Growing delays usually mean an unrecoverable cause like an invalid token — fix the credential rather than waiting out the retry.