Remote Control: questions/prompts stop appearing in app mid-session

Description

When using /remote-control to bridge a CLI session to the Claude mobile app (claude.ai/code), the app stops receiving new content mid-session. The app hangs — no new text, tool results, or interactive prompts (e.g., AskUserQuestion) appear. The CLI terminal side continues working normally.

Reproduction

Environment:

• Claude Code v2.1.76
• Windows 11 Pro (10.0.26200)
• App: Claude mobile app (iOS)

Steps:

1. Start a Claude Code session in the terminal
2. Run /remote-control — app connects and shows the session
3. Interact normally — first few exchanges transfer fine
4. At some point mid-session, the app stops updating entirely
5. New questions, text output, and tool prompts no longer appear in the app
6. The terminal side continues working — user can still respond locally

Observed in two scenarios:

• Scenario A: After ~15-20 rapid tool calls (file reads, greps, edits), subsequent AskUserQuestion prompts did not appear in the app
• Scenario B: In a separate conversation with minimal tool use, the question prompt itself failed to transfer — no heavy tool usage involved

This rules out tool-call volume as the sole trigger. The bridge appears to silently disconnect or stop forwarding messages.

Expected behavior

All session output (text, tool results, interactive prompts) should continue appearing in the app for the duration of the session, or the app should show a disconnection/reconnection indicator.

Diagnostic info

• No bridge session debug log is produced when using /remote-control inside an existing session (only claude remote-control --verbose from a separate terminal produces logs)
• A separately spawned claude remote-control --verbose bridge connects fine (WebSocketTransport: Connected) — suggesting the transport layer works, but the in-session bridge drops silently
• v2.1.76 changelog mentions fixes for "sessions silently dying when the server reaps an idle environment" — this may be a related but distinct issue since the session is actively in use, not idle

Suggestion

• Add reconnection/retry logic for the in-session /remote-control bridge
• Surface a visible indicator in the app when the bridge connection is lost
• Consider producing debug logs for in-session /remote-control (not just the standalone claude remote-control subcommand)