claude-code - 💡(How to fix) Fix Remote-control client doesn't receive completion signal for /clear [1 comments, 2 participants]

Summary

When /clear is executed from a remote-control client (iPad in my case), the remote client does not receive a signal that the command completed. The session appears stuck on the remote side, even though the local/host session has cleared successfully.

Repro

1. Connect to a Claude Code session via remote control (iPad).
2. Send /clear from the remote client.
3. Observe: the remote client never gets a "session cleared" / completion event back, so the UI appears to hang. Subsequent input from the remote feels stuck until something else round-trips.

Expected

The remote-control client should receive the same completion signal that the local TUI gets when /clear finishes, so it can render the cleared state and accept the next input.

Actual

No signal arrives at the remote client. Workaround: type a trivial follow-up prompt (e.g. hi) to force a round-trip that unsticks the remote.

Notes

• May affect other built-in slash commands that don't produce a model turn — worth auditing the set.
• A model-side workaround isn't viable: after /clear the model has no memory of the prior turn, so it can't condition an acknowledgment on "previous input was /clear".

Environment

• Client: iPad remote control
• Host: macOS (darwin 25.3.0), zsh