Dash documentation
Configuration Options
Where Dash keeps its state and what you can change.
The config file
All persistent settings live in ~/.dash/config.json (your home directory). It is created on first save. Dash reads it at startup and writes it after each change made in the TUI.
Schema and defaults
{
"providers": {
"nvidia": {
"apiKey": "", // stored encrypted on disk, empty until you set it
"model": "" // selected model id; empty = use the default
}
}
}apiKey— empty default; encrypted with AES-256-GCM when persisted.model— empty default; set from the/modelspopup.- If the file is missing or corrupted, Dash falls back to the empty default structure and continues to run.
Editing the config
You can edit config.json manually, but the supported way to change provider settings is the /providers and /models commands. If you write an unencrypted raw key into the file yourself, Dash still loads and re-encrypts it on the next save.
Everything on disk
| Path | Purpose |
|---|---|
| ~/.dash/config.json | Provider settings (encrypted key, selected model). |
| ~/.dash/sessions.json | Conversation history shown by /sessions. |
| ~/.dash/memory.md | Persistent private memory (max 32 KB, yours to inspect). |
| <project>/.dash/checkpoints/ | Snapshots taken before file edits for rollback. |