The envless command ships in @goenvless/cli. Install it with npm i -g @goenvless/cli@latest.
Usage
envless whoamiCalls /cli/me with the stored token and prints the verified profile. Use it to confirm which account a CI runner or shared shell is using before syncing secrets.
$ envless whoami
✔ Signed in as jane@acme.dev
› Jane Doe
› id: usr_01HZ...Offline / cached profile
If the call fails for any reason other than a 401, timeout, outage, bad gateway, whoami falls back to the profile cached in ~/.envless/config.json and says so, since that copy is only as current as your last successful call. The exit code is still 0 so it doesn't break scripts that just need to surface the email.
$ envless whoami
⚠ API unreachable (Request timed out). Showing the cached profile.
› jane@acme.dev
› id: usr_01HZ...Not signed in
If no session exists locally, whoami exits with code 1 and points you to envless login.
$ envless whoami
✗ Not signed in. Run envless login to authenticate.Invalid session
If the server rejects the token (revoked, expired, or user deleted), whoami reports the failure and exits 1. Re-authenticate with envless login.
A 401 also deletes ~/.envless/config.json outright, so the token, the cached profile and every cached workspace key go with it. The next command reports "Not signed in", and after logging back in you run envless passphrase set again.