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
1
Run veil login
--device-name, the CLI generates one from your hostname (for example, macbook-pro-a3f2).2
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.
3
Pairing confirmed
Once you approve, the CLI prints a summary:Sandbox credentials are issued immediately. Live credentials are issued only after you have completed production KYC.
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.Check your session
Log out
Manage devices from the dashboard
Paired devices appear in the dashboard under Settings → Paired Devices. From there you can see all active device pairings and revoke individual ones. If a mode’s key is revoked or expired, the CLI prompts you to runveil mode <other> to continue in the unaffected mode, or veil login to restore the revoked one.