[BUG] Desktop sidebar never marks Remote Control (CLI-started) sessions as unread when they produce output

What happens

I run many Claude Code sessions as terminal CLI processes started with claude --remote-control, and monitor them from the Claude desktop app sidebar.

When one of these sessions finishes a turn while I'm viewing a different session, its sidebar dot goes back to the empty (idle) state. It never shows the blue unread dot. So there's no way to tell at a glance which sessions have new output I haven't read.

The unread state itself works for these sessions: right-click > Mark as unread turns the dot blue, and it clears when I open the session. It just isn't set automatically when new output arrives.

Expected

A Remote Control session that produces a new assistant message while it isn't the open session should get the blue unread dot, the same as a session started in the desktop app.

Steps to reproduce

1. Start two or more sessions with claude --remote-control <name> in separate terminals.
2. Open the Claude desktop app and view session 1.
3. Send session 2 a prompt, switch back to session 1, and let session 2 finish.
4. Session 2's dot goes from blinking (working) back to empty, with no blue unread dot.
5. Right-click session 2 > Mark as unread. The dot turns blue, which shows the unread state is supported for this session type.

Environment

• Claude desktop app 2.7032.0 (6c468a), Windows
• Claude Code CLI 2.1.280 (Windows 10 Pro, native install), sessions started with --remote-control
• About 16 concurrent sessions

Related

• #67568 and #64193 (dot semantics; yellow doesn't clear on read)
• #96047 (read state is per install and not synced across devices)
• #85882 and #78429 (Remote Control status not shown in session lists)