Overview

The Ingrain CLI is configured through conf.toml files. It reads each location below and deep-merges them in order — later entries override earlier ones:

1. User config (lowest priority). Path resolves per platform:
   • Linux / macOS: $XDG_CONFIG_HOME/ingrain/conf.toml if XDG_CONFIG_HOME is set, otherwise $HOME/.ingrain/conf.toml.
   • Windows: %APPDATA%\ingrain\conf.toml.
2. Project walk. Inside a git repo, the CLI walks from your current directory up to the repo root and picks up every .ingrain/conf.toml along the way, ordered from repo root → CWD (closer-to-CWD wins). Outside a git repo, only <cwd>/.ingrain/conf.toml is consulted.

On top of that:

• Environment variables — INGRAIN_PROXY_URL overrides the matching [upgrade] key at runtime, and INGRAIN_SYNC_URL / INGRAIN_API_TOKEN override the matching [context] keys.

Sections

Section	What it configures
[upgrade]	The proxy URL ingrain upgrade pulls from.
[context]	Sync URL + API token for ingrain context.

Finding your conf.toml

ingrain config prints the path to your user-level conf.toml so you can open it in your own editor:

ingrain config

The file is created and seeded with the full annotated reference by install.