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

# ev login

> Authenticate the CLI with your Enver API token.

# ev login

Saves your API token to `~/.enver/config.json` so all subsequent commands are authenticated.

## Usage

```bash theme={null}
ev login [token]
```

## Arguments

| Argument | Required | Description                                                                                                                |
| -------- | -------- | -------------------------------------------------------------------------------------------------------------------------- |
| `token`  | No       | Your `env_live_...` API token. If omitted, the CLI opens the dashboard in your browser and prompts you to paste the token. |

## Examples

```bash theme={null}
# Pass token directly
ev login env_live_ae3af653af37f337b0221d79260abbd4cd789e3c4b7b3e6414e71dd80e1be5d4

# Interactive (opens browser)
ev login
```

## Output

```
TOKEN:  env_live_ae3af653...
✓ Successfully logged in! Session token saved.
```

## Where tokens are saved

The token is stored at `~/.enver/config.json`:

```json theme={null}
{ "token": "env_live_..." }
```

This file is read by both the CLI and the VS Code extension.

<Note>
  Tokens are scoped. Ensure your token has at least `write:secrets` scope if you intend to push secrets. See [Token Scopes](/api-reference/authentication#scopes).
</Note>