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

  1. Start a Claude Code CLI session
  2. Connect Remote Control from another device
  3. Have a conversation long enough that auto-compact triggers
  4. Remote Control disconnects (observed in CLI output)
  5. Reconnect Remote Control (/remote-control twice — disconnect then reconnect)
  6. Send a message from the remote device
  7. CLI receives and processes the message, generates a response
  8. Response is NOT sent back to the remote device
  9. 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

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗