Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] /clear from iOS Remote Control doesn't refresh the iOS view (workaround: /quit + respawn) [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#53721•Fetched 2026-04-28 06:48:48
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
0
Author
marcelofariasmarcelofarias
Participants
github-actions[bot]github-actions[bot]marcelofariasmarcelofarias
Timeline (top)
labeled ×5commented ×1

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.

Root Cause

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.

Fix Action

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.

RAW_BUFFERClick to expand / collapse

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.

extent analysis

TL;DR

The issue can be mitigated by implementing a mechanism to refresh or update the iOS Remote Control view after the /clear command is executed.

Guidance

  • Investigate the communication protocol between the iOS app and the claude process to understand why the iOS view is not updating after /clear.
  • Verify that the /clear command is correctly clearing the local conversation history and that the issue lies in the synchronization of this state with the iOS app.
  • Consider implementing a callback or notification mechanism to notify the iOS app when the local conversation history is cleared, triggering a refresh of the iOS view.
  • Review the related issues (#45801, #45803) to see if there are any insights or potential solutions that can be applied to this problem.

Example

No code snippet is provided as the issue does not contain sufficient technical details to create a specific example.

Notes

The provided workaround using a respawn loop is functional but not ideal. A more robust solution would involve modifying the claude process or the iOS app to properly handle the /clear command and update the iOS view accordingly.

Recommendation

Apply a workaround, such as the provided respawn loop, until a more permanent solution can be implemented to properly synchronize the iOS view with the local conversation history after the /clear command is executed.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#ssr#model download#tokenizer error#conversation history

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [BUG] /clear from iOS Remote Control doesn't refresh the iOS view (workaround: /quit + respawn) [1 comments, 2 participants]