Bitwarden is non functional

[asm0dey]

Extension name

bitwarden

Description

The Raycast bitwarden extension is non-functional on Linux under Vicinae. Two distinct problems combine to block normal use:

1. Wrong-OS CLI download. On first launch, the extension auto-downloads a Bitwarden CLI (bw) binary. On Linux it pulls the Windows build instead of the Linux one, so authentication never completes — the launched binary cannot run. (This blocks login entirely; reproducible from a clean Vicinae install.)

2. Performance: bw is spawned per request. The extension shells out to the bw CLI for every operation (list, get, totp, …). Each spawn pays the Node + bw startup cost. On a vault with ~1800 items, list/search/TOTP probing become unusably slow (multi-second latencies per keystroke or per command). A long-running session-store / agent design would avoid this; the current approach does not scale beyond small vaults.

Both behaviours render the extension unfit for actual day-to-day Bitwarden use on Linux — login can't succeed, and even if the binary issue is fixed, the per-call spawn pattern is too slow on real-world vault sizes.

Tested on Raycast?

I didn't test on Raycast

Steps to reproduce

1. Install Vicinae on Linux (version 0.20.14 below).
2. Install the Raycast bitwarden extension via the Vicinae raycast-compat layer.
3. Open the extension and attempt to log in / unlock.
4. Observe: the auto-downloaded bw binary is the Windows build (.exe / PE format) — login fails because the binary cannot execute on Linux.
5. Separately, on a vault with ~1800 items, observe per-keystroke latency caused by per-call bw subprocess spawn.

Vicinae version

0.20.14