CLI reference

Run lifebase for the guided terminal interface. Direct commands perform one operation and exit. Use --help on a command to inspect its available options.

Common commands

Purpose	Command
Sign in with an account and choose a license	lifebase login
Display a code without opening a browser	lifebase login --no-browser
Open the wizard	lifebase
Inspect license and connected vault	lifebase status
List releases available under the current filters	lifebase releases
Include support-ended releases	lifebase releases --include-legacy
Activate a license	lifebase activate
Update the connected vault	lifebase update
Inspect pending update review	lifebase update review
Show CLI version	lifebase --version
Sign out while retaining vault files	lifebase logout

The release list is filtered by license access, content language, CLI compatibility, and support status. Without an exact version, installation or update selects the latest eligible release. The update menu only offers releases newer than the installed vault.

Connect an existing vault

If you copied Lifebase from another device or moved it, connect its current absolute path:

lifebase link --vault /absolute/path/to/lifebase

Linking checks the installed version metadata and remembers the path without reinstalling files, changing agent settings, or contacting the license service. It does not require authentication. The CLI remembers one connected vault path per local configuration.

To operate on a particular vault during an update, use the command’s --vault option. Check lifebase status before changing files if you are unsure which folder is connected.

Update the CLI separately

For an npm installation:

npm install -g @lifebase/cli@latest

Then launch lifebase again. This updates the terminal tool, not the vault content. If you installed the CLI with another package manager, use that manager to update it. See Updating Lifebase for the vault workflow.

Machine-readable commands

Use explicit subcommands with both flags:

lifebase status --json --non-interactive
lifebase releases --json --non-interactive
lifebase update review --unresolved-only --json --non-interactive

Results go to stdout and JSON errors to stderr without terminal styling. Bare lifebase with automation flags does not open a wizard. An exit code of zero can still mean update review is pending; inspect the reported state and next action.

lifebase update can apply changes, including in non-interactive mode. Use status or release discovery when you only intend to inspect availability. Keep license keys out of command arguments, logs, and model prompts; interactive activation provides a hidden input.

Account sign-in requires an interactive terminal and browser approval. login --json --non-interactive returns input_required without starting sign-in. Use existing license-key activate for automation.