Remote Control: responses not sent back to remote device after auto-compact
Resolved 💬 2 comments Opened Apr 7, 2026 by skereking Closed May 19, 2026
Description
After an automatic /compact triggers during a conversation, the Remote Control feature silently breaks. Reconnecting appears to work (shows "connecting…" then connected), but responses are no longer delivered back to the remote device.
Steps to reproduce
- Start a Claude Code CLI session
- Connect Remote Control from another device
- Have a conversation long enough that auto-compact triggers
- Remote Control disconnects (observed in CLI output)
- Reconnect Remote Control (
/remote-controltwice — disconnect then reconnect) - Send a message from the remote device
- CLI receives and processes the message, generates a response
- Response is NOT sent back to the remote device
- Messages sent directly from the CLI work fine — responses appear normally
Expected behavior
After reconnecting Remote Control, responses should be delivered back to the remote device regardless of whether a compact occurred.
Actual behavior
- Remote device sends messages → CLI processes them ✅
- CLI sends responses back to remote device → Never arrives ❌
- CLI-originated messages work fine → Responses appear ✅
Workaround
Use the CLI directly for input after a compact. Disconnecting and reconnecting Remote Control does not fix the issue.
Environment
- OS: Windows 10 Pro 10.0.19045
- Shell: Git Bash
- Claude Code: latest
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗