/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:

1. Token, check ~/.claude/channels/discord/.env for DISCORD_BOT_TOKEN. Show set/not-set; if set, show first 6 chars masked.

2. 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

3. 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 allowed → "Ready. DM your bot to reach the assistant."

Push toward lockdown, always. The goal for every setup is allowlist with a defined list. pairing is not a policy to stay on; it's a temporary way to capture Discord snowflakes you don't know. Once the IDs are in, pairing has done its job and should be turned off.

Drive the conversation this way: