Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Set up and use Bitwarden CLI (bw). Use when installing the CLI, authenticating (login/unlock), or reading secrets from your vault. Supports email/password, API key, and SSO authentication methods.
Set up and use Bitwarden CLI (bw). Use when installing the CLI, authenticating (login/unlock), or reading secrets from your vault. Supports email/password, API key, and SSO authentication methods.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
The Bitwarden command-line interface (CLI) provides full access to your Bitwarden vault for retrieving passwords, secure notes, and other secrets programmatically.
CRITICAL: Always run bw commands inside a dedicated tmux session. The CLI requires a session key (BW_SESSION) for all vault operations after authentication. A tmux session preserves this environment variable across commands.
Verify CLI installation: Run bw --version to confirm the CLI is available Create a dedicated tmux session: tmux new-session -d -s bw-session Attach and authenticate: Run bw login or bw unlock inside the session Export session key: After unlock, export BW_SESSION as instructed by the CLI Execute vault commands: Use bw get, bw list, etc. within the same session
MethodCommandUse CaseEmail/Passwordbw loginInteractive sessions, first-time setupAPI Keybw login --apikeyAutomation, scripts (requires separate unlock)SSObw login --ssoEnterprise/organization accounts After bw login with email/password, your vault is automatically unlocked. For API key or SSO login, you must subsequently run bw unlock to decrypt the vault.
The unlock command outputs a session key. You must export it: # Bash/Zsh export BW_SESSION="<session_key_from_unlock>" # Or capture automatically export BW_SESSION=$(bw unlock --raw) Session keys remain valid until you run bw lock or bw logout. They do not persist across terminal windowsβhence the tmux requirement.
# Get password by item name bw get password "GitHub" # Get username bw get username "GitHub" # Get TOTP code bw get totp "GitHub" # Get full item as JSON bw get item "GitHub" # Get specific field bw get item "GitHub" | jq -r '.fields[] | select(.name=="api_key") | .value' # List all items bw list items # Search items bw list items --search "github"
NEVER expose secrets in logs, code, or command output visible to users NEVER write secrets to disk unless absolutely necessary ALWAYS use bw lock when finished with vault operations PREFER reading secrets directly into environment variables or piping to commands If you receive "Vault is locked" errors, re-authenticate with bw unlock If you receive "You are not logged in" errors, run bw login first Stop and request assistance if tmux is unavailable on the system
VariablePurposeBW_SESSIONSession key for vault decryption (required for all vault commands)BW_CLIENTIDAPI key client ID (for --apikey login)BW_CLIENTSECRETAPI key client secret (for --apikey login)BITWARDENCLI_APPDATA_DIRCustom config directory (enables multi-account setups)
For Vaultwarden or self-hosted Bitwarden: bw config server https://your-bitwarden-server.com
Get Started Guide - Installation and initial setup CLI Examples - Common usage patterns and advanced operations
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.