77a0341f2e
* PM-34506 - Extract LoginStrategyCacheService as single owner of mid-auth cache state * PM-34506 - Refactor LoginStrategySessionTimeoutService: inject cache service, add MessageListener, expose abstraction * PM-34506 - Remove cache state and timer logic from LoginStrategyService, delegate to collaborating services * PM-34506 - Register LoginStrategyCacheService and LoginStrategySessionTimeoutService in all client DI contexts * PM-34506 - Components read loginSessionTimeout$ from LoginStrategySessionTimeoutServiceAbstraction * PM-34506 - Add tests for null cache, and non-API error cache-clear paths in LoginStrategyService * PM-34506 - Add sessionTimeout test for logInNewDeviceVerification with no cached session * PM-34506 - Rename abstractions to follow Default prefix convention (no Abstraction suffix) * PM-34506 - Use fake timers in startSessionTimeout test to eliminate flaky date assertion * PM-34506 - Move registerTaskHandler into DefaultLoginStrategySessionTimeoutService constructor, remove registerSessionTimeoutTask * PM-34506 - PR feedback - DefaultLoginStrategySessionTimeoutService - make cache clear more resilient. * PM-34506 - 2FA Auth Comp - fix tests * PM-34506 - rename login strategy default service files to include default- prefix Aligns file names with class names and the established codebase convention where default implementations are prefixed with `default-` (e.g. default-logout.service.ts). * PM-34506 - TEMP - Default Login Strategy Session Timeout - adjust to 30 seconds to make QA's life easier. * PM-34506 - DefaultLoginStrategySessionTimeoutService - revert temp change and set LOGIN_SESSION_TIMEOUT_LENGTH back to 5 min |
||
|---|---|---|
| .. | ||
| .vscode | ||
| config | ||
| examples | ||
| scripts | ||
| src | ||
| stores | ||
| .npmignore | ||
| CLAUDE.md | ||
| entitlements.plist | ||
| jest.config.js | ||
| package.json | ||
| project.json | ||
| README.md | ||
| test.setup.ts | ||
| tsconfig.json | ||
| tsconfig.spec.json | ||
| webpack.base.js | ||
| webpack.config.js | ||
Bitwarden Command-line Interface
The Bitwarden CLI is a powerful, full-featured command-line interface (CLI) tool to access and manage a Bitwarden vault. The CLI is written with TypeScript and Node.js and can be run on Windows, macOS, and Linux distributions.
Developer Documentation
Please refer to the CLI section of the Contributing Documentation for build instructions, recommended tooling, code style tips, and lots of other great information to get you started.
User Documentation
Download/Install
You can install the Bitwarden CLI multiple different ways:
NPM
If you already have the Node.js runtime installed on your system, you can install the CLI using NPM. NPM makes it easy to keep your installation updated and should be the preferred installation method if you are already using Node.js.
npm install -g @bitwarden/cli
Native Executable
We provide natively packaged versions of the CLI for each platform which have no requirements on installing the Node.js runtime. You can obtain these from the downloads section in the documentation.
Other Package Managers
- Chocolatey
choco install bitwarden-cli - Homebrew
brew install bitwarden-cli⚠️ The homebrew version is not recommended for all users.
Homebrew pulls the CLI's GPL build and does not include device approval commands for Enterprise SSO customers.
- Snap
sudo snap install bw
Help Command
The Bitwarden CLI is self-documented with --help content and examples for every command. You should start exploring the CLI by using the global --help option:
bw --help
This option will list all available commands that you can use with the CLI.
Additionally, you can run the --help option on a specific command to learn more about it:
bw list --help
bw create --help
Help Center
We provide detailed documentation and examples for using the CLI in our help center at https://help.bitwarden.com/article/cli/.