Configuration Reference
Where Mellow's configuration lives.
Configuration reference
Mellow has three configuration surfaces.
Environment (.env)
Deployment-level settings: tokens, database URL, encryption key, ports, links. The full list is in
. Start from.env.example in the repository. Never commit .env.The Mellow config row (database)
A single row holds the AI settings:
| Field | Meaning |
|---|---|
model | Anthropic model id (default claude-haiku-4-5) |
prompt | System prompt |
temperature | Sampling temperature |
maxTokens | Response token cap |
| feature flags | check-in, coping, ghost, and crisis tool groups |
It is seeded on first migration and edited at runtime with the owner-only /mellow command
(/mellow view, /mellow update, /mellow features, /mellow toggle). The presencePenalty
and frequencyPenalty columns exist for schema compatibility but are inert - the Anthropic API
has no equivalent.
Per-guild and per-user settings (database)
- Per guild:
/guildsettings set- feature toggles, channels, moderator role, language. - Per user:
/preferences set- personality, timezone, reminders, and privacy toggles.
There are no JavaScript config files. Mood options, prompt fragments, and similar data are compiled into the Go binary.
Code generation
Database queries are generated from SQL by sqlc (sqlc.yaml at the repo root, sources in
internal/db/queries, output in internal/db/gen). You only need to run sqlc generate if you
change that SQL.