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

# Configure the CLI

> Manage Valkyrie credentials, endpoints, and sandbox providers.

The CLI stores configuration in `~/.config/valkyrie/valkyrie.yaml`. Every `config` command is in the [`valkyrie config` reference](/reference/cli/config).

## Initialize configuration

```bash theme={null}
valkyrie config init
```

Initialization selects a [hosting mode](/get-started/hosting) and collects its required AWS and tracker credentials.

## Set or remove a value

```bash theme={null}
valkyrie config set <KEY> <VALUE>
```

```bash theme={null}
valkyrie config remove <KEY>
```

Use `config set api_key` only for the Vals API key used by hosted tracker authentication. Benchmark-service credentials use the separate [authentication commands](/benchmarks/authentication).

## Configure sandbox providers

Map a provider name to an AWS Secrets Manager secret:

```bash theme={null}
valkyrie config provider set daytona DaytonaSecrets
```

The first configured provider becomes the default. Change it explicitly with:

```bash theme={null}
valkyrie config provider default daytona
```

List or remove provider mappings with:

```bash theme={null}
valkyrie config provider list
valkyrie config provider remove <name>
```

Select another configured provider for one run with `valkyrie run start --provider <name>`. See [Configure sandbox providers](/get-started/sandbox-providers) for the Daytona secret shape.

## Configure benchmark services

Custom benchmark endpoints and credentials use `config service` and `config auth`. See [Custom benchmark services](/benchmarks/custom-services) and [Benchmark authentication](/benchmarks/authentication).