.env file or the OS environment
(OS takes precedence). All feature-flag values are the lowercase strings
"true" or "false" — not "1" / "0", not booleans, not numbers.
If a variable is marked required and is missing at startup, the Engine
fails to boot.
LLM provider and models
Embeddings
Embeddings always route to OpenAI in the current implementation, regardless of the chat-completion provider. You need an OpenAI key even if you’re using Anthropic or Gemini for chat.Web search (optional)
Storage and catalogs
Asset Directory (MCP)
Learning Centre
Channel state and activity
These control how long execution checkpoints survive and how user activity state transitions.Permissions and sandboxing
Server configuration
Feature flags
All values are the strings"true" or "false" (case-insensitive).
Agent loop
Media handling
Memory and compaction
Sandbox
Other
Conventions
- Booleans are strings. Always
"true"or"false". Never1/0, never baretrue/false, neveryes/no. The Engine’s loader is strict about this on purpose — typos become loud errors instead of silent defaults. - Paths are absolute. Anything that takes a path expects an absolute path inside the container.
- Secrets never go in code. They go in
.env, in your secret manager, or in environment variables passed at runtime.
See also
- Local development quickstart — minimal
.envto get the Engine running. - Production deploy — secret rotation, key rotation, hardened defaults.
- Feature flags catalog — the same flags grouped by feature with rollout history.

