[FEATURE] Claude desktop app: sync read/unread state across devices on the same account

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

This is the Claude desktop app, installed on two machines signed in to the same account. Not the CLI.

Read state is local to each install. I read a task's output on my desktop; the unread dot clears there and stays on my laptop. When I next open the laptop, every task I already read is still flagged, so I either re-open each one to clear it or learn to ignore the indicator entirely.

The dot tracks "opened in this app install," not "seen by me." For anyone running the app on more than one machine that makes it noise rather than signal, and the more devices you use, the less the indicator is worth.

What I checked before filing:

• Settings in the desktop app. Nothing for read state or cross-device sync.
• The help article on using Claude Cowork across web, desktop and mobile (support.claude.com/en/articles/15520349). It covers sessions being available on any device, but says nothing about read state.
• Existing issues. The closest ones are about suppressing or bulk-clearing the dots within a single surface, not about syncing the state between installs.

Proposed Solution

Store read state account-level and sync it, the way the sessions themselves already sync. Opening a task on one device marks it read everywhere.

Concretely: when I open a session or task and its unread dot clears on this machine, that clear propagates, so the same row is already read when I next open the app on another machine.

Alternative Solutions

A Mark all as read action would be a smaller fix that solves most of the pain: the second device could be cleared in one step instead of task by task. Weaker than real sync, since it still requires me to notice and act, but much better than the current state.

Current workaround: open every flagged item on the second machine purely to clear it, or stop relying on the dot at all. I have mostly settled on the second, which is presumably the outcome the indicator is meant to prevent.

Priority

Medium - Would be very helpful

Feature Category

Other

Use Case Example

1. Morning, at my desktop: several Cowork tasks finished overnight. I open each one, read the output, act on it. The dots clear.
2. Afternoon, on my laptop — same account, same app, same tasks: every one of them still shows unread.
3. I cannot tell at a glance which are genuinely new since this morning and which I already handled. The two look identical.
4. With read state synced, step 2 shows a clean list and anything still flagged is actually new.

Additional Context

Environment:

• Claude desktop app 2.2553.1
• Both machines: Windows 11 Home

Related issues:

• #92430 — turn off the unread dot or mark all read in Cowork on the web. Same symptom, different cause: that one is about dots that never carried information in the first place; this one is about a dot that did carry information and was already acted on, on another machine.
• #64193 — closed; notification dot never clearing, no way to configure it.
• #22648 — account-level settings sync. Adjacent, but about settings rather than read state.
• #59641 — session sync across CLI, desktop app and web. Sessions do sync for me; the read state on them does not.