Bitwarden CLI
Overview
choco install bitwarden-cliVersion & Lifecycle
Community Notes
Bitwarden CLI automation, server, and session controls
For managed Bitwarden CLI use, configure the target service before login when needed: bw config server https://vault.example.com points the CLI at a self-hosted Bitwarden server instead of the public cloud service.
For non-interactive automation, Bitwarden documents API-key login with environment variables: set BW_CLIENTID and BW_CLIENTSECRET, then run bw login --apikey. Unlocking the vault returns an exportable BW_SESSION value; pass that session value to later commands rather than prompting inside scheduled tasks or deployment scripts.
On shared, portable, or non-persistent runners, set BITWARDENCLI_APPDATA_DIR so CLI configuration and cached state live in a predictable directory. If exposing the local REST bridge, use bw serve only in a controlled context and bind the hostname/port intentionally. Source: Bitwarden CLI documentation.
Release Notes & Updates
Help us match vulnerabilities
No vulnerability match yet. Pick the right product:
Don’t see it? Paste a CPE
Also known as
Other names people use for this app — helps search and matching.
Sign in to suggest a name.
Packaging Notes
Available via Chocolatey, Homebrew, Snap, and npm (npm install -g @bitwarden/cli). Native executables available in documentation downloads.[2]
