> ## Documentation Index
> Fetch the complete documentation index at: https://docs.elding.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Commands

> Reference for Elding CLI commands.

| Command                 | Purpose                                                                   |
| ----------------------- | ------------------------------------------------------------------------- |
| `elding login`          | Authenticates the CLI through your browser.                               |
| `elding logout`         | Revokes the token and removes it locally.                                 |
| `elding whoami`         | Displays the signed-in email address.                                     |
| `elding status`         | Shows the connection, active set, and proxy status.                       |
| `elding doctor`         | Diagnoses the token, set, keys, and proxy.                                |
| `elding init`           | Links the project to a set.                                               |
| `elding deploy`         | Generates a deployment key and prints the 2 env variables for production. |
| `elding use <name>`     | Changes the active set.                                                   |
| `elding sets`           | Lists accessible sets.                                                    |
| `elding keys`           | Lists key names, never their values.                                      |
| `elding proxy -- <cmd>` | Runs a command behind the secure local proxy.                             |

## Example

```bash theme={null}
elding login
elding init
elding proxy -- node app.js
```

## Deploy to production

`elding deploy` creates a deployment key (visible in the **API Keys** tab) and prints the
two environment variables to add to your host (Vercel, etc.):

```bash theme={null}
elding deploy
# ELDING_REFRESH_TOKEN=eld_rt_...
# ELDING_SET_ID=...
```

<Warning>
  The deployment key is shown only once. Do not run `elding deploy` in a CI with public logs —
  the key would be exposed there. Run it locally and paste the variables into your host's
  environment settings.
</Warning>