Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.envless.cloud/llms.txt

Use this file to discover all available pages before exploring further.

​
Usage

envless login

Starts a device-authorization flow. The CLI prints a one-time code, opens your browser to the Envless dashboard, and polls in the background until you approve the session.

​
What happens

1

Request a device code

The CLI calls /cli/device to mint a short-lived device code and a human-readable user code (e.g. ABC-123).

2

Approve in the browser

Your default browser opens to the verification URL with the code pre-filled. Confirm the code matches the one shown in your terminal, then approve the session while signed in to Envless.

3

CLI receives the token

The CLI polls /cli/token every few seconds. Once approved, the token and user profile are written to ~/.envless/config.json with 0600 permissions (directory 0700).

The flow times out after 10 minutes. If the timer runs out, run envless login again.

​
Already signed in

If a session already exists, envless login is a no-op and prints the current account. Run envless logout first to switch users.

$ envless login
[login] Already signed in as jane@acme.dev
[login] Run `envless logout` first to switch accounts.

​
Where credentials live

PathModeContents
~/.envless/700Per-user CLI state directory.
~/.envless/config.json600Bearer token and cached user profile.

Treat config.json like an SSH key — don’t commit it, don’t sync it to shared machines, and revoke the session with envless logout if it’s ever exposed.

https://mintcdn.com/envless-7b88c948/nR8RUPgNBtCF5SFI/assets/icons/duotone/user.svg?fit=max&auto=format&n=nR8RUPgNBtCF5SFI&q=85&s=f063bb4ca567ae0d17f42251774eea59

Whoami

Inspect the current session.
https://mintcdn.com/envless-7b88c948/nR8RUPgNBtCF5SFI/assets/icons/duotone/sign-out.svg?fit=max&auto=format&n=nR8RUPgNBtCF5SFI&q=85&s=ddfe390346028287941ebf5f38c465e6

Logout

Revoke the session and clear local credentials.