Permission prompts do not forward to remote control client (mobile)

Bug

When using the Claude Code remote control feature (e.g. from a mobile device), permission prompts block on the local terminal rather than forwarding to the remote client.

Steps to reproduce

1. Connect to a Claude Code session via remote control on a mobile device
2. Trigger an operation that requires a permission prompt (e.g. a new tool like WebFetch)
3. The session hangs — the prompt appears on the local terminal, not on the mobile client

Expected behavior

Permission prompts should be forwarded to and actionable from the remote control client, the same way code output and responses are.

Actual behavior

The session silently hangs on the remote client until the user physically goes to the terminal and approves the prompt.

Context

Permission prompts work correctly in normal (non-remote) terminal sessions. The issue is specific to the remote control client.