Remote Control session becomes unresponsive after first command from mobile app

Description

After activating /remote-control from an existing Claude Code session on Linux and pairing the mobile Claude app, the session becomes unresponsive after the first command sent from mobile. The "working" spinner (bamboozling, clauding, etc.) is shown briefly, then disappears with no output on either device. Subsequent messages also trigger the spinner but produce no response.

Environment

• Claude Code version: 2.1.119
• Plan: Max
• OS: Linux (Ubuntu 5.15.0-174-generic)
• Auth: claude.ai account (not API key)
• Mobile: Claude app

Steps to reproduce

1. On Linux server, run claude in a project directory
2. Type /remote-control — session activates, URL shown (no QR code displayed)
3. Open the session from the Claude mobile app — chat history visible on both devices
4. Send a command from mobile
5. Spinner appears, then disappears with no response
6. Send another simple message like "hello" — same behavior

Expected

The assistant response should render on both PC terminal and mobile app.

Actual

No output rendered on either device. Session appears hung.

Workaround

Kill the session and restart claude + /remote-control.