[FEATURE] Discord plugin: option to show full command in permission prompts by default

Problem Statement

When managing Claude Code remotely via the Discord channels plugin, permission prompts (approve/deny for bash commands, file edits, etc.) arrive in DMs with the command truncated. You have to tap "cmore" on every single prompt to see what command is actually being requested before you can make an informed approve/deny decision.

This adds an extra interaction to every permission prompt, which is painful when commands are flying in rapidly during active sessions. On mobile especially, it turns what should be a quick glance-and-tap into a multi-step process: (1) see truncated prompt, (2) tap cmore, (3) read full command, (4) approve or deny.

For users running headless Claude Code sessions managed entirely through Discord, the permission prompt is the only visibility into what the agent is doing. The truncated default actively works against informed decision-making.

Proposed Solution

Add a configuration option to always display the full command/tool details in Discord permission prompt messages by default — no "cmore" expansion needed.

This could be:

• A flag in access.json like "expandPermissionPrompts": true
• A plugin-level setting
• A per-channel option

The truncated view could remain the default for backwards compatibility. Power users managing sessions remotely need the full context upfront.

Alternative Solutions

• Configurable truncation threshold — show the full text for commands under N characters, only truncate very long ones
• Send full command as a follow-up message — immediately after the truncated prompt, send a second message with the full command text
• Currently working around this by pre-authorizing as many command patterns as possible in settings.local.json to reduce the number of prompts, but novel commands still require the cmore→read→approve flow

Priority

Medium - Would be very helpful

Feature Category

MCP server integration

Use Case Example

I run two Claude Code sessions on a headless Debian server (ThinkPad), managed entirely via Discord from my phone. One session handles personal infrastructure, the other handles a creative project with a collaborator.

When my agent is doing exploratory work — SSH probes, file searches, git operations — I get a flood of permission prompts in my DMs. Each one currently requires:

1. See truncated permission prompt in Discord DM
2. Tap "cmore" to expand
3. Read the full command
4. Tap approve or deny

Steps 2-3 are unnecessary friction. With expandPermissionPrompts: true, the flow becomes:

1. See full command in permission prompt
2. Tap approve or deny

This is especially important when multiple people share approval rights on a session (via allowFrom) — collaborators who didn't set up the session need maximum context to make safe approval decisions.

Additional Context

• Related: #32952 (notification hooks should include tool details) — that issue covers the hooks system, but the same UX gap exists in the Discord plugin's built-in permission relay
• The Discord plugin already has the full command data available (it renders on "cmore" tap), so this is a presentation change, not a data pipeline change
• Discord message length limit (2000 chars) could be a concern for very long commands, but most bash commands are well under that