[BUG] Sessions stay marked unread in Desktop app after being viewed (macOS)
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
Description
In the Claude Code Desktop app on macOS, sessions continue to show as unread
after I've opened and read them. I worked through every session step by step
in the past days, yet all of them still appear as unread in the conversation
list. There is no UI to manually clear the unread state.
Expected behavior
A conversation that has been opened and viewed should be marked as read.
Alternatively, the app should provide an explicit "Mark all as read" action
(for example in the list header or via right-click menu).
Actual behavior
Conversations remain flagged as unread indefinitely, even after being opened
and scrolled through. No UI exists to clear the state, either per conversation
or in bulk.
Environment
- Claude Code Desktop app (standalone)
- macOS: 15.5.7
- App version: Claude 1.3883.0 (93ff6c) 2026-04-21T17:24:01.000Z
Suggested fix
Either (a) automatically clear the unread state when a conversation is opened
and scrolled, or (b) add a manual "Mark all as read" action at the list level.
What Should Happen?
A conversation that has been opened and viewed should be marked as read.
Alternatively, the app should provide an explicit "Mark all as read" action
(for example in the list header or via right-click menu).
Error Messages/Logs
Steps to Reproduce
- Open the Claude Code Desktop app (standalone, macOS).
- Have several completed conversations in the sidebar.
- Click into each conversation, scroll through, and read the full contents.
- Return to the conversation list.
Claude Model
None
Is this a regression?
Yes, this worked in a previous version
Last Working Version
_No response_
Claude Code Version
2.1.85 (Claude Code)
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Terminal.app (macOS)
Additional Information
_No response_
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗