bitwarden

Automate Bitwarden CLI login, unlock, and secret retrieval in tmux sessions.

Updated Jan 31, 2026

Search Tags:#tmux #secrets #bitwarden #bw #password-management #vault-unlock

Ready to run

npx skills add https://github.com/JimiHFord/openclaw-bitwarden --skill bitwarden-jimihford

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bitwarden
Source: https://github.com/JimiHFord/openclaw-bitwarden/tree/main
Command: npx skills add https://github.com/JimiHFord/openclaw-bitwarden --skill bitwarden-jimihford

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bw, jq, curl, tmux, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Bitwarden CLI workflows can be repetitive and error-prone when logging in, unlocking vaults, and retrieving secrets. This Skill automates and unifies these steps, reducing manual effort and improving security by consistently using a dedicated session.

Core Features & Use Cases

Manage Bitwarden login, vault unlock, and secret retrieval inside a single, tmux-backed workflow.
Generate passwords, fetch usernames, and obtain TOTP codes via bw to streamline credential management.
Use in local development with Vaultwarden for testing secret workflows and automation scenarios.

Quick Start

Install the Bitwarden CLI, set up a local Vaultwarden instance, unlock the vault, and start retrieving secrets with bw.

Frequently Asked Questions about bitwarden

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate Bitwarden CLI login and unlock within a tmux session?▼

You can automate Bitwarden CLI login and unlock by running a workflow that verifies bw presence, manages the BW_SESSION environment variable, and uses a dedicated tmux session to persist authentication across commands.

How does tmux persist Bitwarden vault authentication across multiple commands?▼

Tmux persists Bitwarden vault authentication by maintaining a dedicated session where the BW_SESSION variable remains active, allowing you to retrieve secrets and generate passwords without repeatedly unlocking the vault.

Do I need to install jq and curl to use Bitwarden CLI for secret retrieval?▼

Yes, you need jq and curl installed alongside the Bitwarden CLI and tmux, as these dependencies support the workflow to fetch usernames, obtain TOTP codes, and parse secret data.

What is the best way to manage BW_SESSION for local development with Vaultwarden?▼

The best way to manage BW_SESSION for Vaultwarden testing is to use a unified workflow that logs in, unlocks the vault, and exports the session variable within a persistent tmux-backed environment.

Can I generate passwords and retrieve TOTP codes using bw without manual vault unlocks?▼

Yes, once the vault is unlocked and the BW_SESSION is active within the tmux session, you can generate passwords, fetch usernames, and obtain TOTP codes via bw without manual unlocks.

Why does my Bitwarden CLI workflow repeatedly ask for credentials during script execution?▼

Your Bitwarden CLI workflow asks for credentials because the BW_SESSION is not persisted; using a dedicated tmux session to manage the vault unlock state resolves this repetitive authentication issue.