bw-vaultSet 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.
Install via ClawdBot CLI:
clawdbot install startupbros/bw-vaultInstall Bitwarden CLI (npm):
Install Bitwarden CLI (npm)Install Bitwarden CLI (brew):
brew install bitwarden-cliInstall Bitwarden CLI (choco):
Install Bitwarden CLI (choco)Requires:
Grade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Accesses system directories or attempts privilege escalation
sudo mvCalls external URL not in known-safe list
https://bitwarden.com/help/cli/Audited Apr 18, 2026 · audit v1.0
Generated Mar 21, 2026
In a CI/CD pipeline, developers use the Bitwarden CLI to securely inject API keys and database passwords into deployment scripts without hardcoding secrets. The CLI runs in a tmux session within the pipeline container, fetching secrets from the vault and setting them as environment variables for applications during deployment.
IT administrators in large organizations utilize the CLI to manage and audit shared credentials for servers, network devices, and SaaS platforms. They authenticate via SSO, retrieve passwords programmatically for automated scripts, and ensure compliance by locking sessions after use, reducing manual password handling risks.
Financial analysts use the CLI to access encrypted credentials for data sources like banking APIs or financial databases during automated reporting. By running commands in a dedicated tmux session, they securely retrieve TOTP codes and passwords, ensuring sensitive financial data remains protected in audit logs.
Healthcare IT staff deploy applications that require access to patient data systems, using the CLI to fetch database credentials and API keys from a vault. This ensures HIPAA compliance by avoiding secret exposure in code, with sessions managed in tmux to maintain security across operations.
E-commerce developers integrate the CLI into their backend services to dynamically retrieve payment gateway keys and shipping API tokens. By using API key authentication, they automate secret rotation and reduce downtime, with the CLI running in tmux sessions on production servers for reliable access.
Bitwarden offers a freemium model with paid tiers for advanced features like SSO, audit logs, and priority support. Revenue is generated through monthly or annual subscriptions from individuals, teams, and enterprises, with pricing based on user count and feature access.
For large organizations, Bitwarden provides enterprise licenses with custom SLAs, dedicated support, and on-premise deployment options like Vaultwarden. Revenue comes from one-time license fees or annual contracts, often including training and integration services.
Bitwarden monetizes its CLI and API by offering premium integrations with third-party tools like CI/CD platforms, password managers, and security suites. Revenue is generated through partnership agreements, API usage fees, or commissions from marketplace sales.
💬 Integration Tip
Always run the CLI in a tmux session to preserve the BW_SESSION environment variable, and use API key authentication for automated scripts to avoid interactive logins.
Scored Jun 19, 2026
Self-hosted auth for TypeScript/Cloudflare Workers with social auth, 2FA, passkeys, organizations, RBAC, and 15+ plugins. Requires Drizzle ORM or Kysely for D1 (no direct adapter). Self-hosted alternative to Clerk/Auth.js. Use when: self-hosting auth on D1, building OAuth provider, multi-tenant SaaS, or troubleshooting D1 adapter errors, session caching, rate limits, Expo crashes, additionalFields bugs.
Clerk integration. Manage Users, Organizations. Use when the user wants to interact with Clerk data.
Clerk auth with API Keys beta (Dec 2025), Next.js 16 proxy.ts (March 2025 CVE context), API version 2025-11-10 breaking changes, clerkMiddleware() options, webhooks, production considerations (GCP outages), and component reference. Prevents 15 documented errors. Use when: API keys for users/orgs, Next.js 16 middleware filename, troubleshooting JWKS/CSRF/JWT/token-type-mismatch errors, webhook verification, user type inconsistencies, or testing with 424242 OTP.
Sentry API integration with managed authentication. Monitor errors, issues, and application performance. Use this skill when users want to list issues, retrieve events, manage projects, teams, or releases in Sentry. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a Sentry connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Sentry action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with Sentry examples; they add no Sentry capability - Sentry is not an event source, a trigger cannot read Sentry data, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe).
Host static files on subdomains with optional authentication. Use when you need to serve HTML, images, CSS, JS, or any static content on a dedicated subdomain. Supports file upload, basic auth, quota management, and automatic SSL via Caddy. Commands include sf sites (create/list/delete), sf upload (files/directories), sf files (list/delete).
Download YouTube videos by URL in various resolutions using a pay-per-use API with credit-based authentication and no charge on failed downloads.