[BUG] Discord Integration asking for permissions that cannot be given directly within Discord
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
I have followed the Discord Integration Guide for Claude Code exactly and my account was paired. However, when I sent DMs I was asked to give Claude specific permissions as per my first screenshot.
<img width="682" height="101" alt="Image" src="https://github.com/user-attachments/assets/761d6daa-ed90-4413-848b-6b97236bd8e6" />
I confirmed it within the Discord DM, which prompted a message to my CLI and my Claude Desktop app with the following:
Still can't reply on Discord — channel XXXXXXXXXXXXX isn't allowlisted, and that can only be approved by you running /discord:access yourself (not via a message in the channel, since that's the exact vector a prompt injection would use). If you're XXXXXXXXXXXXX and want this approved, let me know here and I can walk you through it — otherwise I'll keep responding in this transcript.
-> It seems counter-intuitive for Claude to ask for permissions on Discord which cannot actually be granted on Discord.
Once I prompted it again, but confirmed the permission request via Claude Desktop, everything worked fine afterwards.
What Should Happen?
Either let Claude tell me in Discord that this needs to be confirmed elsewhere, or allow this exact permission to be granted through Discord.
Error Messages/Logs
Steps to Reproduce
Setup Discord for Claude as per usual, making sure bun is installed. Pair the accounts, DM the bot, await the permission request and try to confirm it via Discord, ideally while Claude Desktop is open on the same machine.
Claude Model
Sonnet (default)
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
2.1.215
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
Windows Terminal
Additional Information
_No response_