Skip to main content

Requirements

  • Node.js 22.12 or later, below 25. Check your version with node --version.
  • npm, which comes with Node.js.
  • An OS keychain for storing your API key: Keychain on macOS, Credential Manager on Windows, or a Secret Service provider such as GNOME Keyring or KWallet on Linux. You don’t need one if you only use the SABAOTH_API_KEY environment variable, as in CI.
If you need to install or switch Node.js versions, a version manager such as nvm, fnm or Volta makes it easy.

Install

The CLI is published to npm as @sabaoth-cloud/cli. It installs a command called sabaoth.

Check the installation

sabaoth --help lists the available commands. If your shell says command not found, see Troubleshooting.

Update

Install the latest version over the top of the current one:
Your saved login and organization selection are kept.

Uninstall

Sign out first so your API keys are removed from the OS keychain, then remove the package:
The CLI also keeps a small context file holding organization IDs and names, but no keys. To remove it too, delete the sabaoth folder at the location shown in the table below.

Where the CLI stores data

The CLI stores two things on your machine. API keys go into the OS keychain under the service name com.sabaothcloud.sabaoth, with one entry per organization (account org:<organization-id>). There is no plain-text fallback. If the keychain can’t be reached, commands that need it fail rather than writing the key somewhere else. Context, meaning the organizations you have signed in to and which one is selected, goes into a JSON file. It contains no secrets. Run sabaoth config to see the exact path on your machine.

API endpoint

The CLI always talks to https://api.sabaothcloud.com. There is no flag or environment variable to point it somewhere else. This is deliberate: an override would make it too easy to send an API key to the wrong server by mistake.

Next step

Sign in

Create an API key and log in.