Changelog
What changed, release by release. Every detail is in CHANGELOG.md.
1.2.2 — 2026-11-18
Chrome extension: saves your sign-ins
After a successful sign-in the extension asks to save it, or to update a password that changed. Account ID, region and the page’s other fields come along, and AutoFill now fills every saved field back by its name. Saving while the vault is locked needs no master password: the sign-in is encrypted to the vault’s public key and added at your next unlock. More →

Touch ID and passkey unlock (web UI and extension)
Add a passkey in Settings → Security & lock, then unlock with Touch ID, Windows Hello or a security key. The master password keeps working. More →

Mobile: Face ID, Touch ID and fingerprint unlock
The app opens with your face or finger. The master password stays in the phone’s secure hardware and is released only after a match. More →

Android: concealer as the password autofill service
Sign-in fields in every app and browser offer “Fill with concealer”; you unlock, pick the sign-in and it is filled. New sign-ins can be saved the same way. More →

A redesigned Settings page
One page with a side menu: Security & lock, Appearance, AI agents, Browser extension, Integrations, Sync, Portability, Backup, About.

Also new
- A short film for every interface, on its page: Chrome extension, CLI, Web UI, TUI, MCP, Mobile.
- A Created column in the web UI, next to Updated, and sorting by date columns works again.
- The extension popup opens on your 20 most used secrets; “Fill with concealer” and “Save sign-in to concealer” in the right-click menu.
- Mobile auto-lock gains 15 min, 30 min and 1 hour; the master password box gets the cursor.
cer run [scope] -- <cmd>accepts the usual--separator.
1.2.1 — 2026-11-17
- Web UI: the secrets table header no longer covers the open filter dropdowns.
1.2.0 — 2026-11-16
- Chrome extension: AutoFill on sign-in pages, agent sign-in (
request_web_login) with your approval, an unlock page, and a context menu. See the full changelog.