feat(bitwarden): add Bitwarden extension#271
Conversation
|
@asm0dey closed the other PR as was getting messy with all the changes, new PR here. Added sends support! |
edmogeor
force-pushed
the
main
branch
2 times, most recently
from
06d0244 to
cd3ab9e
Compare
|
@edmogeor I tried to use the TOTP functionality and got following error: |
|
Also, it takes incredible time to even try to copy it; it seemingly freezes or just thinks for a very long time |
@asm0dey Try rebuilding now from the source. I couldn't replicate the CLI issue - I might suggest using the log out command to clear the cache, and running To fix the issue with loading, I think it must've been because I was calling the bw cli directly for every item to get the TOTP code, instead of just using the secret to locally generate them (secrets stored using libsecret) - meaning with a long list multiple calls to the bw cli were happening at the same time. This new approach with otpauth seems to be a lot more performant and should fix your issues. It's totally possible bw cli was crashing/timing out because of the multiple instances causing the error you saw so hopefully this fixes it. |
|
Nah, doesn't seem to work for me. I see "Loading…" constantly, and nothing ever copies |
Hey @asm0dey - can i ask you try again after a logout, rebuild from source and restart (i've made a changed to the caching as to my guess at the issue). I've also added more robust error logging, so can i ask you run: and submit a bug report on the main branch at https://github.com/edmogeor/vicinae-bitwarden/issues/new?template=bug_report.yml so we can diagnose further there? Much appreciated! |
…password - Master password field clears its error on the next keystroke so a second attempt is no longer silently blocked. - Logged-out cold open paints the unlock form immediately instead of waiting on `bw status`; falls back to a single login+retry if the CLI turns out to be unauthenticated. - Reopening after Log Out no longer flashes a loading screen between the optimistic form and the post-login form.
- Split item-utils into focused modules (toast, item-list, item-actions, item-form) and removed the single-use json-utils helper. - Collapsed 22 defensive catch blocks in bw-executor into two conversion seams, replaced the getLoginActions push ladder with a declarative spec, and extracted shared hooks/helpers (useCardFields, runInitialLoad, validateSendForm, requireApiCreds, parseDateFromHours). - Tightened tsconfig (noUncheckedIndexedAccess, noImplicitOverride). - CI: fallow health badge now reflects static code health only, not churn-weighted hotspots.
|
@asm0dey did you manage to try the latest version? Would be great to see if we can fix your issue so we can get this merged |
|
Sorry, didn't have time yet :(
…On Sun, 24 May 2026 at 18:31, George Edmonds ***@***.***> wrote:
*edmogeor* left a comment (vicinaehq/extensions#271)
<#271 (comment)>
@asm0dey <https://github.com/asm0dey> did you manage to try the latest
version? Would be great to see if we can fix your issue so we can get this
merged
|
2 participants
Summary
Keyboard-driven access to a Bitwarden vault. Unlock once with your master password, then search and copy passwords, usernames, TOTP codes, and manage Sends - all from the launcher.
Commands
Requirements
The Bitwarden CLI (
bw) must be installed and on PATH.libsecret-toolsis required for secure session storage in the system keyring. Supports US cloud, EU cloud, and self-hosted servers (with optional custom CA certificate).Configuration
bitwarden.com(US),bitwarden.eu(EU), or Self-hostedhttps://vault.example.com~/Downloads)Validation
Notes
assets/extension_icon.png(512×512)