Persist Inbox "Show unread only" toggle across visits

Problem

The Inbox's Show unread only toggle resets to off whenever the Inbox view is remounted. Users who prefer an unread-only Inbox have to enable it again after navigating away, reopening the Inbox, or restarting Buzz.

The current Desktop implementation stores this only as component state and initializes it to false:

buzz/desktop/src/features/home/ui/HomeView.tsx

Lines 109 to 110 in 485d03a

    
           const [filter, setFilter] = React.useState<InboxFilter>("all"); 
        
           const [unreadOnly, setUnreadOnly] = React.useState(false);

Steps to reproduce

Open the Inbox.
Enable Show unread only.
Navigate away from the Inbox and return, or restart Buzz and reopen the Inbox.

Current behavior

Show unread only is off again.

Expected behavior

Buzz remembers the user's last choice and restores the toggle to the same checked or unchecked state the next time the Inbox opens.

Acceptance criteria

Enabling Show unread only remains effective after navigating away from and back to the Inbox.
The enabled state is restored after restarting Buzz.
Disabling the toggle updates the saved preference so it remains disabled on subsequent visits.
Users without a saved preference retain the current default of off.
Automated coverage verifies preference restoration and the default/fallback behavior.

fix: persist Inbox 'Show unread only' toggle across sessions

Backlog tracking note: #3682 is the active implementation for this issue. It replaces the Inbox's component-only unreadOnly state with a versioned localStorage-backed preference and includes coverage for the default, restoring both values, and persisting a later disable. The PR is currently open; contributors should coordinate there instead of starting a duplicate fix.

Still reproduces on Buzz Desktop 0.5.10 (macOS), 2026-08-12. Independent confirmation from another user.

The toggle has to be re-enabled every time. There is no way to keep an unread-only Inbox as the default view.

Confirming the cause is unchanged on main today rather than assuming: desktop/src/features/home/ui/HomeView.tsx:112 is still

const [unreadOnly, setUnreadOnly] = React.useState(false);

so the state is still component-only and still initialises to false, exactly as the issue describes.

Flagging for whoever is triaging: #3682 is the linked fix and it has been open since 2026-07-30 with no activity since 2026-07-31. If it has stalled, this is worth freeing up for a different contributor rather than leaving it blocked on a PR that is not moving.

This still reproduces on Desktop 0.5.23 and current main (HomeView.tsx:113 initializes unreadOnly with useState(false)). For anyone running an unread-only Inbox it has to be re-enabled on every visit, which makes the Inbox much harder to use day to day.

There are already three open fixes: #3682 (small, tested, mergeable since Aug 19), #6105, and #6151 (changes requested). Could a maintainer pick one of them - #3682 looks like the smallest path - so this doesn't stall further? Happy to test a build.

fix(desktop): remember Inbox unread-only choice (#7672)

#7672 merged.

fix(desktop): remember Inbox unread-only choice (block#7672)

Navigation Menu

Repository navigation

Persist Inbox "Show unread only" toggle across visits #3669

Problem

Steps to reproduce

Current behavior

Expected behavior

Acceptance criteria

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

	const [filter, setFilter] = React.useState<InboxFilter>("all");
	const [unreadOnly, setUnreadOnly] = React.useState(false);

Persist Inbox "Show unread only" toggle across visits #3669

Description

Problem

Steps to reproduce

Current behavior

Expected behavior

Acceptance criteria

Activity

BradGroux commented on Jul 31, 2026

rrggrr commented on Aug 12, 2026

flowq-C commented on Sep 14, 2026

ngthuydiem commented on Sep 23, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions