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

# CLI configuration

> Understand local credentials, endpoint overrides, and debugging preferences.

Most users need only `edgee auth login` and `edgee settings`. Use overrides when your administrator supplies a private gateway or a diagnostic configuration.

## Profiles and credentials

The CLI stores profile configuration and credentials in `~/.config/edgee/credentials.toml`. Keep the file private. Use [profile commands](/docs/cli/authentication) rather than copying credentials between machines or editing a stale example file.

## Environment overrides

| Variable                | Purpose                                              |
| ----------------------- | ---------------------------------------------------- |
| `EDGEE_API_URL`         | Override the gateway endpoint used for model traffic |
| `EDGEE_CONSOLE_URL`     | Override the console used for browser authentication |
| `EDGEE_CONSOLE_API_URL` | Override the management API endpoint                 |
| `EDGEE_MCP_URL`         | Override the Edgee MCP endpoint                      |
| `EDGEE_NO_UPDATE_CHECK` | Disable the automatic update check                   |

Gateway URL resolution uses an environment override first, then the profile override, then the organization's gateway configuration, then the default. Ask your administrator for the endpoint appropriate to your deployment.

```bash theme={"dark"}
EDGEE_API_URL=https://gateway.example.com edgee launch claude
```

This example changes the endpoint for one shell command. It does not deploy a gateway. Follow [Self-hosting](/docs/self-hosting/overview) for deployment and authentication requirements.

## Confirm an override

Launch one request and verify it in the intended gateway's logs and console. If traffic appears in the wrong environment, check exported environment variables and the active profile before changing organization settings.

To return to the default in a POSIX shell, use `unset EDGEE_API_URL` and review any persisted profile override. On PowerShell, use `Remove-Item Env:EDGEE_API_URL` for the process environment.