Does not remember folder or search vault settings over lock
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13.8k
- Forks
- 2k
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 397
Description
Steps To Reproduce
In the new 2026.4.0 release, the client resets the search vault string. Therefore, if you have good security posture, and lock the vault after a few minutes, when you unlock it, it wont show you the items that you had searched on. This means that you have to keep searching for this everytime which is frustrating and reducing the user experience. This worked up until 2026.4.0.
Also, can you please do the same remembering for the folder as well. It is annoying to have to go into a folder everytime on unlock as well. Searching for an item does not always show you want you want, especially if you are constantly moving between different logins in a folder. Searching is cumbersome and not easy.
Locking the vault is a security measure. It should not frustrate the user that unlocking it means reverting back to a newly opened application.
How to test:
- Search for an item
- OR move to a folder
- Wait for the vault to lock
- Unlock vault
- Search and folder are reverted
Expected Result
The application should open exactly where it was when unlocking from a lock. Upon opening the vault it could either revert to initial state, or revert to last state.
Actual Result
Need to perform search, or find folder again - reducing usability and adding frustration.
Screenshots or Videos
No response
Additional Context
No response
Operating System
Windows
Operating System Version
11
Installation method
Direct Download (from bitwarden.com)
Build Version
2026.4.0
Issue Tracking Info
- I understand that work is tracked outside of GitHub. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in the Windows desktop client's lock and unlock flow, then trace how the active search vault and folder selection are handled across that transition. Use the listed reproduction steps to verify the behavior; done means unlocking restores the prior search and folder state without weakening vault locking.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100