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

# Config and auth

> Configure model selection and provider access for the Voss harness.

Voss keeps harness configuration narrow in v0.1. The most important setting is the preferred model.

## Show or edit config

```bash theme={"theme":"github-dark"}
voss config --show
voss config
```

The default config path is:

```text theme={"theme":"github-dark"}
~/.config/voss/config.toml
```

## Recall and context options

Code recall injection can be disabled when you want the harness to skip the automatic recall
section:

```toml theme={"theme":"github-dark"}
[code_recall]
inject = false
```

Context packing can also be disabled globally, or per run with `voss do --no-pack`:

```toml theme={"theme":"github-dark"}
[context]
enabled = false
```

## Switch model in a session

Inside the REPL:

```text theme={"theme":"github-dark"}
/model
/model <model-id>
```

The selected model can be persisted to config.

## Login flow

Use provider CLIs first, then tell Voss which auth source to prefer when needed:

```bash theme={"theme":"github-dark"}
claude login
codex login
voss do --auth=claude "summarize this repo"
voss do --auth=api "summarize this repo"
```

Inside the REPL, `/login` shows local auth status and refreshes existing credentials when possible.

## Provider safety

Session persistence must not store provider credentials. Credentials should remain in provider-specific auth storage or environment configuration.

<Tip>
  Run `voss doctor` after changing provider or model settings.
</Tip>