Login workflow help
Daily-driver workflow with Bitwarden on a vault where every login is 2FA + federated (Sign in with Apple/Google)?
I'm moving to qutebrowser as my daily browser on OpenBSD (dwm). Password manager is Bitwarden with the bw CLI, and I've got the qute-bitwarden userscript filling username/password via fake-key.
My problem: every single login I have uses two-factor, and a large share go through "Sign in with Apple" or "Sign in with Google" rather than a plain password box. On those federated pages the fake-key fill doesn't land in the field at all, and the TOTP step is a separate manual action anyway.
For people running qutebrowser full-time with a setup like this:
- How do you actually handle the federated Apple/Google sign-in pages? Does fake-key work for you there, or do you route those logins elsewhere?
- What's your TOTP flow? --totp to clipboard then paste, a separate --totp-only bind, or something else?
- Which qute-bitwarden variant is the most reliable one in 2026? There are several forks (JonnyHaystack and others). Which do you run?
- Is anyone genuinely doing 100% of logins through qutebrowser when everything is 2FA, or is the realistic answer "qutebrowser for browsing, another browser for the awkward logins"?
OpenBSD specifics if it matters: no keyctl, using dmenu instead of rofi, xclip for clipboard.
Blunt answers welcome. I want to know if this is a solved workflow or if I'm fighting the tool.