Feature name
Alternative unlock methods for bw unlock after initial login
Feature function
All other Bitwarden clients — browser extension, desktop app, and mobile — support alternative
unlock methods after the initial login. The CLI is the only client that always requires the full
master password, both for bw login and bw unlock.
This creates unnecessary friction for interactive workflows where the vault needs to be unlocked
repeatedly throughout a session.
Proposed unlock methods (priority order):
- PIN — a short, locally-verified code set after
bw login - Biometrics — delegate to the OS (Windows Hello, Touch ID)
- Passkey — longer term, aligns with Bitwarden’s passkey direction
The security boundary at bw login (full master password required) should remain unchanged.
Alternative unlock methods would only be available after the initial authenticated session is
established — exactly as implemented in other clients.
Related topics + references
- Unlock with PIN (closed) — narrower request, closed 2025
- Persist CLI unlock without BW_SESSION (closed) — related, closed 2025
- GitHub: bitwarden/clients — upstream CLI repo