Generator Settings lost after logout

[DenBesten]

Maybe this feature request would be more to your liking then. If so, go vote for it!

Pinned (and collapsible) search queries to customize Vault view

I do think it would be really helpful if the search capabilities were enhanced as follows: Add the ability to pin search queries [image] so that we can have many saved/visible for quick, easy access. 2.Be able to collapse/expand [image] both our own search results and the automatic system ones, saving state when the vault is closed. To the advanced search, add sorting options (last used, alphabetical, etc.). When something in is in the search bar, the “All Items” name is not really a…

[Neuron5569]

@Nail1684

So, you mean the other settings

If we have problems communicating, just imagine… At the bottom of the extension, the tabs “Generator” and “Settings” are separate. Hence, Settings’ settings aren’t lost for me, but Generator’s settings are.

[Nail1684]

@Neuron5569

Settings’ settings

Indeed, I only now see that you wrote it like that. So it seems, my glasses were dirty today, after all.

[DenBesten]

@Neuron5569

At the bottom of the extension, the tabs “Generator” and “Settings” are separate. Hence, Settings’ settings aren’t lost for me, but Generator’s settings are.

Thanks for this clarification. It also was unclear to me that you were exclusively referring to the generator settings being less persistent than the rest of the settings.

To hopefully avoid confusion, I updated the topic title to more clearly incorporate where this topic has headed.

Now: Generator Settings lost after logout
Was: Browser extension logged out

[grb]

@DenBesten

Now: Generator Settings lost after logout

I still see the following (even if I clear browser history or open a completely different browser):

 

Do I need to clean my glasses, again?

[DenBesten]

This time, I think the problem was on my side. Looks like save took effect in my browser but did not sync. Now that I came back in, it reverted for me too, so I applied it again… and it shows up in a different browser too.

[mutilator]

Will we have a reset again?

[Nail1684]

@mutilator

Will we have a reset again?

Probably not – usually that doesn’t happen – but we’ll see.

[mutilator]

Looks like nothing happened this time.

[Nail1684]

Indeed… I think the update to 2025.6.0 (server) was revoked:

(–> Releases · bitwarden/server · GitHub)

PS: I guess due to that, the web vault seems to be also still on 2025.5.1. – But I don’t know if they updated and reversed the updates - or if they detected the bug before the update could take place?

[mutilator]

Webvault has been converted?

[Nail1684]

@mutilator

Webvault has been converted?

That’s the release - it’s not revoked, yes.

But if you open the web vault (vault.bitwarden.com / vault.bitwarden.eu) and scroll to the bottom, you can see that it is still on version 2025.5.1.

PS: Ah, a corrected server version 2025.6.1 was now released…

[mutilator]

What i see.

[Nail1684]

Yup, with updating the “servers” to 2025.6.1, the web vault was then also updated to 2025.6.0.