Skip to content

Install ​

geslar needs a Geslar account on a Premium, Family, Business or Enterprise plan. Agents and CI service accounts (machine identities) need a plan that includes them; on a Family plan they belong to the plan's owner.

npm ​

The CLI is distributed through npm only.

sh
npm install -g @geslar/cli
geslar --version

Node.js 22 or later is required. Windows, macOS and Linux are supported.

Where it keeps its state ​

The local key that seals your session is kept in the operating system's keychain where there is one: Windows Credential Manager, the macOS Keychain, or on Linux a Secret Service (GNOME Keyring, KWallet, KeePassXC). --key-storage (or GESLAR_KEY_STORAGE) chooses:

  • auto (the default): the keychain when it works. If the keychain cannot be used at all, the CLI says so and keeps the key in a file protected by a local password instead. Once a key file exists, the file keeps being used.
  • keychain: only the OS keychain; an error if it does not work.
  • file: the key file, even where a keychain works.
sh
geslar login --key-storage file     # or: GESLAR_KEY_STORAGE=file

The local password (file mode) is separate from your master password and is asked for in the terminal. Switching between keychain and file requires geslar logout first.

Linux without a Secret Service. The keychain library does not fail there; it falls back to the kernel keyring (keyutils). The CLI notices this the first time it stores the key and warns you: the key lives in the kernel keyring of this login session and does not survive a restart of the computer, so you would have to sign in again. Use --key-storage file to keep it. An agent profile cannot be created in that situation at all, and geslar mcp serve needs the OS keychain.

Uninstall ​

sh
geslar logout
geslar agent remove <name>     # for each agent profile on this machine
npm uninstall -g @geslar/cli