Filesystem paths

Config directory: `~/.deltaforge/`. Config file: `config.toml`. History: `history` (1000 entries). Sessions: `sessions/<YYYYMMDD-HHMMSS>.jsonl`.

Category: configuration

Description

## Overview The CLI keeps all persistent state under a single per-user directory, `~/.deltaforge/`, resolved via `dirs::home_dir()`. The directory is created on first use. There are four known entries: the config file, the REPL history file, the sessions subdirectory, and anything the user adds by hand. ## Behavior - `~/.deltaforge/` is the config directory. The CLI creates it on demand when it needs to write history or a session file. Nothing else is written here unless a feature explicitly says so. - `~/.deltaforge/config.toml` is the TOML configuration file (optional). See `CLI_CONFIG_FILE`. - `~/.deltaforge/history` is the REPL command history. It is a reedline file-backed history capped at 1000 entries. Both the classic REPL and the interactive shell append here. - `~/.deltaforge/sessions/` holds one JSONL file per interactive shell session, named `<YYYYMMDD-HHMMSS>.jsonl`. Each line records one statement plus its outcome. `--resume` reads from this directory. - Paths are stable, the CLI does not honor `XDG_CONFIG_HOME` or `XDG_STATE_HOME`. The directory lives under `$HOME` on every supported platform. ## Compatibility - The config directory is safe to delete. The CLI recreates it and falls back to built-in defaults on the next run. - Session JSONL files are written only by the interactive shell. The classic REPL (`--classic`) does not emit them, so `--resume` will not find sessions produced by classic runs.

Examples

~/.deltaforge/config.toml
~/.deltaforge/history
~/.deltaforge/sessions/20260419-140001.jsonl

Pitfalls

See Also

Open in interactive docs →   DeltaForge home →