Config reference
What you'll find here
How Craik v0.1.0 is configured — environment variables, the local home, the setup / doctor / update commands, project-level context discovery rules, Stigmem and GitHub env vars, and pre-publication validation.
Env-var-driven, with a structured local home.
Configuration lives in the environment and in CRAIK_HOME.
Project-local .craik/ directories are opt-in only.
Local state
CRAIK_HOME~/.craikCraik stores runtime state in a SQLite database under
CRAIK_HOME/state/. Project-local .craik/ directories are opt-in
only and are not created by the current CLI.
Setup commands
craik setupcraik.gateway_config. Prints secrets_written = false and does not collect API keys, channel tokens, webhook secrets, or bearer credentials.craik doctorcraik updateContext discovery
Project profiles can store documentation discovery overrides through
craik project add.
--discovery-exclude <glob>--discovery-include <glob>craik case build accepts the same options as one-off user overrides
for a single case-file build. Craik always starts from conservative
defaults that skip generated, dependency, build, cache, and
archive-heavy paths. The resulting case file records active rules and
skipped paths in context_budget.
Stigmem
CRAIK_STIGMEM_URLCRAIK_STIGMEM_API_KEYCRAIK_STIGMEM_TIMEOUT5.0Never commit API keys.
Craik redacts token-shaped values from persisted payloads and command output, but the discipline starts with you.
GitHub
CRAIK_GITHUB_TOKENGITHUB_TOKENCRAIK_GITHUB_TIMEOUT5.0The GitHub adapter is read-only in v0.1.0.
Validation
Run before publishing changes:
uv run --python 3.12 --extra dev ruff check .
uv run --python 3.12 --extra dev mypy
uv run --python 3.12 --extra dev pytest
uv run --python 3.12 --extra dev craik policy test