Bug: /remote-control session permanently stuck on usage limit prompt — no recovery path from mobile app

Bug Description

When using /remote-control with the Claude Code mobile app, hitting the usage limit causes an interactive prompt on the local terminal that cannot be dismissed through the remote control channel. The session is permanently blocked until someone physically accesses the machine.

Steps to Reproduce

1. Start Claude Code on a desktop/server with /remote-control and --dangerously-skip-permissions
2. Connect to the session from the Claude Code mobile app
3. Run a long-running task that eventually hits the usage limit
4. Observe: usage limit prompt appears on the local terminal, the mobile app session freezes

Expected Behavior

The usage limit event should either:

• Be surfaced through the remote control channel so it can be dismissed remotely, or
• Be handled non-interactively (wait and resume, or exit cleanly) so the session doesn't block

Actual Behavior

The session blocks indefinitely on the local terminal. The mobile app has no way to interact with this prompt. There is no recovery path without physical access to the machine.

Why This Is a Bug

The remote control protocol creates a reasonable expectation that the session can be fully managed remotely. A blocking local prompt that is invisible and unresolvable through the remote channel breaks this contract.

Related Feature Request

See #41502 for the corresponding feature request (--wait-on-usage-limit flag).

Environment

• Claude Code with /remote-control
• Client: Claude Code mobile app
• Platform: Windows (but the issue is protocol-level, likely affects all platforms)