[FEATURE] Remote Control: allow expanding permission prompts on iOS to see the full command before approving

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

When using the Claude Code Remote Control feature from the Claude iOS app, permission approval prompts (Allow / Deny) only display approximately the first 100 characters of the command that Claude Code wants to execute. There is no way to expand, scroll, or otherwise view the full command text.

This means users must approve or deny tool calls — including potentially destructive bash commands, file writes, and other system operations — without being able to see what they are actually approving. The user is effectively forced to "go on faith" that the command is safe.

This is a significant usability and security concern. The entire point of the permission system is to give the user informed control over what Claude Code does on their machine. Truncating the command in the approval UI undermines that by making informed decisions impossible from mobile.

Proposed Solution

The permission prompt in the Claude iOS app (when connected to a Remote Control session) should allow the user to tap or expand the command preview to see the full command text before choosing Allow or Deny. This could be implemented as:

• A "Show more" / expand button that reveals the full command inline
• A scrollable region within the prompt that contains the complete command
• A tap-to-expand modal or sheet displaying the full command text

The full command text should be viewable regardless of length — whether it is a short ls or a multi-line bash script.

Alternative Solutions

_No response_

Priority

High - Significant impact on productivity

Feature Category

Other

Use Case Example

Remote Control is designed for monitoring and controlling Claude Code sessions when away from the terminal. Without the ability to review the full command, users are left with two bad options:

1. Blindly approve — accepting commands they cannot fully read, which defeats the purpose of the permission system and introduces security risk
2. Deny everything — which blocks the session and defeats the purpose of Remote Control

This is especially important for long or complex bash commands, multi-line file edits, and any command involving paths or arguments that extend beyond the visible ~100 characters.

Additional Context

_No response_