Configuration Options

Every setting in Daystrom — with its CLI flag, env var, and default value.

---

Config Cascade

Settings resolve through a four-level cascade (highest priority wins):

1. CLI flags (--provider, --model, etc.)
2. Environment variables (LLM_PROVIDER, LLM_MODEL, etc.)
3. Config file (~/.daystrom/config.json)
4. Zod schema defaults

Info

The ~ prefix in any path value is expanded to $HOME at load time.

---

Config File

Optional JSON file at ~/.daystrom/config.json. Keys use camelCase matching the Zod schema.

{
  "llmProvider": "claude-api",
  "llmModel": "claude-opus-4-6",
  "scanConcurrency": 3,
  "propagationDelayMs": 15000,
  "maxMemoryChars": 5000,
  "memoryEnabled": true,
  "accumulateTests": false,
  "dataDir": "~/.daystrom/runs",
  "memoryDir": "~/.daystrom/memory"
}

---

All Settings

Setting	CLI Flag	Env Var	Default	What it does
llmProvider	--provider	LLM_PROVIDER	claude-api	LLM provider selection
llmModel	--model	LLM_MODEL	per-provider	Model override
scanConcurrency	--	SCAN_CONCURRENCY	5	Parallel scan requests (1--20)
propagationDelayMs	--	PROPAGATION_DELAY_MS	10000	Wait after topic deploy (ms)
maxMemoryChars	--	MAX_MEMORY_CHARS	3000	Memory injection budget (500--10000)
memoryEnabled	--no-memory	MEMORY_ENABLED	true	Toggle cross-run learning
accumulateTests	--accumulate-tests	ACCUMULATE_TESTS	false	Carry forward tests across iterations
maxAccumulatedTests	--max-accumulated-tests	MAX_ACCUMULATED_TESTS	unlimited	Cap on accumulated test count
dataDir	--	DATA_DIR	~/.daystrom/runs	Run state directory
memoryDir	--	MEMORY_DIR	~/.daystrom/memory	Learning store directory

Provider Default Models

Provider	Default Model
claude-api	claude-opus-4-6
claude-vertex	claude-opus-4-6
claude-bedrock	anthropic.claude-opus-4-6-v1
gemini-api	gemini-2.5-pro
gemini-vertex	gemini-2.5-pro
gemini-bedrock	gemini-2.5-pro

Concurrency tuning

scanConcurrency above 5 risks AIRS rate limiting. Increase cautiously.

Propagation delay

AIRS needs time to propagate topic changes. The default 10 seconds is usually sufficient; increase if scans fail immediately after deployment.