[BUG] Remote Control (desktop app): shows old conversation from before /clear or compaction, then jumps to the current state much later (sometimes never)

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report
• [x] I am using the latest version of Claude Code (2.1.296 installed; the affected long-running processes were started on 2.1.293-2.1.296)

What's Wrong?

In sessions where /clear or a compaction (manual /compact or auto-compact) has happened, the Claude desktop app (Code tab, via Remote Control) often loads an old part of the conversation from before the /clear or compaction (hours to days old) instead of the current one. It stays there as if buffering, and after a long while it suddenly jumps to the current state. Sometimes it never seems to catch up until the CLI process is restarted or Remote Control is reconnected.

The terminal always shows the correct, current conversation, and the work itself is not affected. Only the app's view is behind.

What Should Happen?

According to the Remote Control docs ("What connected devices see", https://code.claude.com/docs/en/remote-control), after /clear the conversation should reset on connected devices too, and after a compaction they should show where the conversation was compacted. The app should show the current conversation, not an older part of it.

Error Messages/Logs

No error message is shown in the app or in the terminal.

Observations from the local transcripts (~/.claude/projects/...):

• Within one CLI process the bridgeSessionId stays the same across /clear, so the conversations before and after /clear share one server session. The old view always comes from an earlier part of that same server session.
• All affected sessions in October had been running for days. In the latest case the process had been running since Oct 8 and the server session had lastSequenceNum 4826. It looks as if the app replays the stored history from an early point before catching up.

Steps to Reproduce

Not reproducible on demand yet. This is the setup where it keeps happening:

1. Start Claude Code in a long-lived tmux session with claude --remote-control <name> (remoteControlAtStartup: true is also set).
2. Use the session only from the Claude desktop app (Code tab) via Remote Control for several days, with many turns.
3. Run /clear or /compact (or let auto-compact happen) a few times in the same process.
4. Keep using the session from the desktop app. At some point the app shows an old part of the conversation from before a /clear or compaction, stays there, and later suddenly jumps to the current state (or never catches up until the CLI is restarted or Remote Control is reconnected).

Seen at least 5 times since Oct 5 across three sessions (three times on Oct 10 alone), plus twice in late August.

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.296 (Claude Code) installed; the affected processes were started on 2.1.293-2.1.296 and kept running

Platform

Anthropic API (Claude Max subscription)

Operating System

macOS

Terminal/Shell

Other (tmux with zsh; the sessions are never used from the terminal directly, only from the desktop and mobile apps via Remote Control)

Additional Information

• Claude desktop app 2.31226.1.
• Restarting the CLI process (new Remote Control session) always gives a clean view.
• In the latest case, another short-lived CLI session on the same machine (also auto-connected to Remote Control) connected and disconnected 2-4 minutes before it happened. Not sure whether that is related.