Configuration¶

Daystrom is designed to work with minimal setup. All settings have sensible defaults — only credentials are strictly required.

Config Cascade¶

Settings are resolved in priority order (highest wins):

CLI flags  >  Environment variables  >  ~/.daystrom/config.json  >  Zod defaults

This means a --provider flag always beats an env var, which always beats the config file.

Config File¶

For settings you use across every run, create ~/.daystrom/config.json:

~/.daystrom/config.json

{
  "llmProvider": "claude-api",
  "scanConcurrency": 5,
  "propagationDelayMs": 10000,
  "maxMemoryChars": 3000,
  "memoryEnabled": true
}

LLM Providers¶

Provider	Config Value	Default Model	Auth
Claude API	`claude-api`	`claude-opus-4-6`	`ANTHROPIC_API_KEY`
Claude Vertex	`claude-vertex`	`claude-opus-4-6`	GCP ADC
Claude Bedrock	`claude-bedrock`	`anthropic.claude-opus-4-6-v1`	AWS creds
Gemini API	`gemini-api`	`gemini-2.5-pro`	`GOOGLE_API_KEY`
Gemini Vertex	`gemini-vertex`	`gemini-2.5-pro`	GCP ADC
Gemini Bedrock	`gemini-bedrock`	`gemini-2.5-pro`	AWS creds

Claude Vertex region

The claude-vertex provider defaults to the global region, not us-central1. Override with GOOGLE_CLOUD_LOCATION if needed.

For detailed provider setup, see LLM Providers.

Tuning Parameters¶

These settings control how Daystrom interacts with AIRS and the memory system.

Env Var	Config Key	Default	What it does
`SCAN_CONCURRENCY`	`scanConcurrency`	`5`	Parallel scan requests per batch (1--20)
`PROPAGATION_DELAY_MS`	`propagationDelayMs`	`10000`	Wait time after topic deploy, in ms
`MAX_MEMORY_CHARS`	`maxMemoryChars`	`3000`	Character budget for memory injection (500--10000)
`MEMORY_ENABLED`	`memoryEnabled`	`true`	Toggle cross-run learning on/off
`ACCUMULATE_TESTS`	`accumulateTests`	`false`	Carry forward tests across iterations
`MAX_ACCUMULATED_TESTS`	`maxAccumulatedTests`	unlimited	Cap on accumulated test count
`DATA_DIR`	`dataDir`	`~/.daystrom/runs`	Where run states are saved
`MEMORY_DIR`	`memoryDir`	`~/.daystrom/memory`	Where learnings are stored

Concurrency vs. rate limits

Keep scanConcurrency at 5 or lower to avoid AIRS rate limiting. Increase only if your tenant has elevated quotas.

Propagation delay

AIRS needs time to propagate topic changes. The default 10 seconds works for most cases. Reduce for faster iteration during development; increase if you see stale scan results.

Data Locations¶

Path	Purpose
`~/.daystrom/config.json`	Persistent configuration
`~/.daystrom/runs/`	Saved run states (JSON per run)
`~/.daystrom/memory/`	Cross-run learnings (JSON per category)