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

# Configuration

> Understand SelfTune's local state, environment overrides, and credential boundaries.

SelfTune creates local configuration and state during initialization. Prefer
Desktop settings or version-matched CLI workflows over editing stored JSON by
hand.

## Inspect configuration safely

Run the health check first:

```bash theme={null}
selftune doctor
```

It reports the active SelfTune version, detected harnesses, discovery and hook
health, local runtime state, and configuration problems without requiring you
to memorize internal fields.

## Local state

The default SelfTune state root is `~/.selftune/`. It may contain configuration,
the local database, evaluation artifacts, runtime manifests, and operational
history. Individual files are implementation details and may change between
releases.

Before moving, restoring, or deleting the state root:

1. stop or detach any registered local service;
2. identify the SelfTune version that created the state;
3. preserve the full directory rather than selecting one database file; and
4. verify the restored runtime with `doctor`.

## Environment overrides

Use environment overrides for ephemeral CI or server configuration. Record the
variable names in the automation that owns them and avoid mixing multiple state
roots for the same background runtime. Inspect the installed command's `--help`
for supported overrides.

## Credentials

Local dashboard authentication is separate from Cloud or Remote Library
credentials. When the platform supports a credential vault, remote tokens are
stored there. Do not place tokens in `SKILL.md`, source control, command
examples, or shared diagnostic output.

## Telemetry and remote connections

Anonymous product telemetry, local agent-history ingestion, and Remote Library
upload are separate settings. Review each independently. Disabling one must not
be described as disabling the others.

See [Privacy and permissions](/guides/privacy-and-permissions) before changing a
data boundary.

Inspect configuration through the installed product before reading or editing
internal files. Report the active state root and ownership. Do not expose
tokens or raw histories. Ask before changing hooks, telemetry, credentials,
background ownership, remote endpoints, or deleting state. Verify changes with
`doctor` and the relevant status command.