Stop Re-selecting Your Notification Filters — v0.1.317
Stop Re-selecting Your Notification Filters
A small change with a big daily impact — v0.1.317
If you work through a busy notification inbox, you'll know the drill: open the panel, toggle "Show unread only", maybe pick a notification type, work through a few items, close the panel — and the next time you open it, everything has reset back to defaults.
That's the friction we've fixed in v0.1.317.
What's Changed
The notification panel now remembers your filter selections. Your "Show unread only" preference and your active notification type filter are both saved to localStorage the moment you set them. When you reopen the panel — whether that's 30 seconds later or the next morning — it reopens exactly how you left it.
Two filters, two keys, zero re-selecting:
notif_filter_unread— remembers whether you had "unread only" switched onnotif_filter_type— remembers which notification type you were focused on
Why This Matters
For agents managing high notification volumes, filter state is part of a working rhythm. Losing it every time the panel closes is a small interruption — but it happens many times a day. Multiplied across a team, it adds up to real friction and real time.
Persisting that state is a minimal change with a meaningful reduction in repetitive interaction.
The Reset Button
To keep things transparent and user-controlled, we've added a "Clear filter preferences" button inside the panel. If you ever want to return to the default (all notifications, all types), one click clears both your in-session filters and the stored preferences.
Under the Hood
This follows the same pattern already used by the work-queue time filter (work-queue.tsx), bringing the notification panel in line with how filter persistence works elsewhere in the platform. Consistency in implementation means consistent, predictable behaviour for users across different parts of the product.
Released as part of our ongoing usability improvements. See the changelog for full details.