The CLI uses browser-based device pairing. You runDocumentation Index
Fetch the complete documentation index at: https://docs.useveil.co/llms.txt
Use this file to discover all available pages before exploring further.
veil login, confirm in the browser, and the CLI writes credentials to the OS keychain. You stay paired until you run veil logout or revoke the device from the dashboard.
Pair your machine
Run veil login
--device-name, the CLI generates one from your hostname (for example, macbook-pro-a3f2).Confirm in the browser
The CLI prints a pairing code and opens a verification URL in your browser. If the browser doesn’t open automatically (headless or SSH environments), copy the URL from the terminal.Sign in to Veil and approve the pairing request. The page shows the device name and which modes will be available.
Credential storage
Credentials are stored in the OS keychain using@napi-rs/keyring, under the service name veil-cli. A single keychain entry holds both sandbox and live keys (where available), along with the active mode, device name, and account email.
On Linux, the keychain backend requires
libsecret (e.g. GNOME Keyring). If the keychain is unavailable or locked when veil login runs, the CLI exits with a hint pointing at libsecret. veil login opens a browser to complete pairing, so it isn’t designed for headless CI use.