[BUG] /clear from iOS Remote Control doesn't refresh the iOS view (workaround: /quit + respawn)

Resolved 💬 3 comments Opened Apr 27, 2026 by marcelofarias Closed Apr 30, 2026

Summary

Running /clear from the iOS Remote Control view executes successfully on the local claude process (the conversation is cleared on the laptop), but the iOS app continues to display the prior conversation history. There appears to be no way to clear the iOS-side view in place.

Steps to reproduce

  1. Start claude on the laptop with Remote Control enabled (default-on via settings).
  2. Connect to that session from the iOS Claude app.
  3. Build up some conversation history visible in the iOS view.
  4. Run /clear from the iOS app.
  5. Observe: command completes, local state is cleared, but the iOS view continues to render the prior conversation.

Expected

After /clear, the iOS Remote Control view should reflect the empty/fresh session, matching the cleared local state.

Actual

The iOS view still shows the prior conversation. The only way to get a clean view from the phone is /quit, which terminates the local process — defeating the in-place clear.

Workaround

A respawn loop on the laptop (while true; do claude; done) so that /quit from iOS terminates and immediately re-launches a fresh claude, which the iOS app then sees as empty. Functional but obviously not how /clear is supposed to behave.

Environment

  • Platform: macOS (Darwin 25.4.0)
  • Remote Control: enabled by default in settings
  • Multiple parallel claude instances running in separate terminals (each individually attachable from iOS)
  • Client: iOS Claude app

Related

  • #45801 / #45803 — different symptom (/clear hangs) but same general area: iOS view not syncing with local cleared state. Both auto-closed as duplicates and now locked, so filing a new issue per the auto-close message's guidance.

View original on GitHub ↗

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