Command-line workflows
Use Vaulter from the terminal with less friction and clearer next steps.
The CLI is designed for developers who want a clean path: install, sign in, run commands, and move back to shipping.
Install
Install the CLI
Start with one global install command, then authenticate in the browser.
npm install -g vaulter
Quick path
Step 1
Install
Add the CLI once and keep it available for local workflows.
Step 2
Sign in
Use browser auth to connect the CLI to your Vaulter account.
Step 3
Run commands
Read from the same hosted vault you manage in Vaulter.
// Get started
A short setup sequence that stays obvious from the first screen.
Inspired by cleaner command-first product pages, the CLI flow now foregrounds the install and sign-in actions before everything else.
Step 1
Install Vaulter
Make the CLI available globally so you can call it from any repo or shell session.
npm install -g vaulter
Step 2
Authenticate in the browser
Connect the CLI to your hosted Vaulter account once, then reuse the session for future commands.
vaulter sign-in
// Common commands
Command groups that are easier to scan and easier to remember.
Instead of a crowded docs wall, the page groups the most useful commands by what you are trying to do next.
Start here
Get Vaulter installed, authenticate once, and connect your terminal to the same Vaulter vault you use on the web.
Install
npm install -g vaulter
Authenticate
vaulter sign-in
Core operations
List, add, inspect, and assemble env output with small, readable commands.
List secrets
vaulter list
Add a key
vaulter add OPENAI_API_KEY sk-... --tag production
View a key
vaulter view OPENAI_API_KEY
Generate env output
vaulter make OPENAI_API_KEY ANTHROPIC_API_KEY
// Typical workflow
Install, authenticate, store, and generate output in one compact loop.
This section makes the first useful developer journey obvious without surrounding it with too many competing blocks.
Step 1
vaulter sign-in
Step 2
vaulter add STRIPE_SECRET_KEY sk_live_... --tag billing
Step 3
vaulter make STRIPE_SECRET_KEY > .env.local
Troubleshooting
Clear answers when something breaks.
Not authenticated
Run `vaulter sign-in` again and complete the browser flow using the same account you use in Vaulter.
Expired session
Refresh local credentials through browser sign-in, then rerun the command that failed.
Wrong API target
Confirm the CLI points to the correct hosted Vaulter environment before generating output.