Release / / with omarchy-bitwarden-0.10.0, omawarden-0.8.0, omarchy-bitwarden-0.10.1, omarchy-bitwarden-0.10.2, omarchy-bitwarden-0.10.3, omawarden-0.8.1, omarchy-bitwarden-0.11.0, omarchy-bitwarden-0.11.1
Omarchy Bitwarden omarchy-bitwarden-0.11.2
Sign in with a hardware security key and complete email or new-device verification.
Before you upgrade to omarchy-bitwarden-0.11.2
3 to fixUpdate to a build reporting a numeric version of at least 0.8.1. `-dev` and VCS suffixes no longer bypass the version gate; unknown versions are rejected.
Use `$XDG_CONFIG_HOME/omawarden/config.json` and `$XDG_DATA_HOME/omawarden/data.json` (defaults under `~/.config` and `~/.local/share`). Legacy files migrate automatically; update direct file references.
Website icons use the configured self-hosted server's icon endpoint. Failed requests use category icons instead of falling back to the public Bitwarden icon service.
Downloads now enforce `max_attachment_size_mb`, defaulting to 500 MiB. Set a suitable positive value for larger files; zero falls back to the default.
Engine 0.8.1 rejects sync responses over 64 MiB and ordinary API JSON responses over 2 MiB instead of reading unbounded responses.
Read the evidence
Settings identify the installed engine source and route AUR updates through the package helper; development builds suppress stable-release downgrade prompts.
Overlay font sizes now follow shared Omarchy `Style` tokens.
What changed in omarchy-bitwarden-0.11.2
Plugin 0.10.0 and engine 0.8.0 add hardware-key and email challenges. Plugin 0.11.0 removes the bundled engine and downloader; 0.11.2 requires numeric engine version 0.8.1+ for stable, development, and VCS builds.
Also: Remember searches across reopen, install missing dependencies, and migrate settings out of the watched plugin folder.
Plugin 0.11.2 requires omawarden >= 0.8.1 on PATH, Omarchy Shell, Secret Service/secret-tool and wl-clipboard; install omawarden-bin or omawarden-git via AUR, or a system binary. Hardware keys require libfido2 tools.
New things you can do
Complete Bitwarden login using a WebAuthn/FIDO2 hardware security key.
The login flow can send or resend email 2FA codes and switch between supported providers.
Reopen the overlay with your previous search, filters, and selected item retained.
The overlay gates access on missing dependencies and offers installation of `omawarden-bin`, `libsecret`, and `wl-clipboard`.
Fixed and improved
Vault cache and settings now live outside the watched plugin directory, preventing sync and configuration writes from triggering shell reload loops.
Seeded by 