/discord:configure — Discord Channel Setup
Writes the bot token to ~/.claude/channels/discord/.env and orients the
user on access policy. The server reads both files at boot.
Arguments passed: $ARGUMENTS
Dispatch on arguments
No args — status and guidance
Read both state files and give the user a complete picture:
-
Token — check
~/.claude/channels/discord/.envforDISCORD_BOT_TOKEN. Show set/not-set; if set, show first 6 chars masked. -
Access — read
~/.claude/channels/discord/access.json(missing file = defaults:dmPolicy: "pairing", empty allowlist). Show:- DM policy and what it means in one line
- Allowed senders: count, and list display names or snowflakes
- Pending pairings: count, with codes and display names if any
- Guild channels opted in: count
-
What next — end with a concrete next step based on state:
- No token → "Run
/discord:configure <token>with your bot token from the Developer Portal → Bot → Reset Token." - Token set, policy is pairing, nobody allowed → "DM your bot on
Discord. It replies with a code; approve with
/discord:access pair <code>." - Token set, someone…
- No token → "Run
