When I choose which columns to make visible and which to hide using “view settings”, which takes some time, those settings to not persist across page reloads. I often find myself reconfiguring the view several times just to be able to browse.

No drop-in plugin exists to stash your Content-Manager “view settings” in localStorage. Every Strapi solution out there persists settings server-side (in the core store) or via config files—none use browser storage.

Why Strapi avoids localStorage for that

• The “gear → view settings” panel already stores changes per-session in the UI only—it resets on refresh or navigation. That’s by design. 

• Permanent configs must be applied via Configure the view → Save, which stores them in the core store (database), not in browser storage.