[BUG] Tool-permission prompts triggered from the mobile app can't be approved on mobile — force a switch to desktop

Summary

When a Claude Code session is driven/monitored from the mobile app (phone) and Claude hits a tool that needs permission (Bash, MCP tools, file writes, etc.), the permission prompt cannot be approved from the phone. Every single approval forces me to switch to the desktop/notebook, approve there, then go back to the phone.

This makes driving a session from mobile impractical for any workflow that uses permission prompts — which in practice is almost all of them (MCP tool calls, Bash commands, edits).

Steps to reproduce

1. Start / attach to a session from the mobile app.
2. Have Claude run something that requires approval (e.g. a Bash command or an MCP tool not on the allowlist).
3. A permission prompt is raised.
4. Try to approve it from the mobile app.

Expected

Approve / deny the permission prompt directly from the mobile app, without touching the desktop.

Actual

The prompt can't be acted on from mobile. I have to go to the desktop/notebook to approve every time, then return to the phone. Constant context-switching.

Impact

The "drive Claude Code from my phone" use case is effectively broken for anything beyond read-only/allowlisted actions — each permission prompt is a hard interrupt that requires another device.

Suggestion

Surface and allow acting on permission prompts (approve / deny / always-allow) from the mobile client itself, mirroring the desktop prompt.