runtime.json files.
Config file overview
JSON config files:
Other config files:
First run
Export variables in the shell, or setENV_FILE=/path/to/mycel.env before starting the service:
runtime.json
Runtime fields
Runtime fields
Memory — pruning and compaction
Memory — pruning and compaction
Pruning trims large tool results:
Compaction summarizes old history via LLM when context fills:
See Memory for full details.
Tool configuration
Tool configuration
Each tool group has an Complete tool catalog:
enabled flag. Both the group and individual tool must be enabled.deferred tools are not injected into every request. The agent discovers them via tool_search when needed — saving tokens in conversations that don’t require task management.Project-level example
Project-level example
explicit runtime overrides:
models.json
Virtual model aliases
Virtual model aliases
Mycel provides four Override a mapping through Settings-backed model configuration:
leon:* aliases:Set via Settings → Models in the Web UI:
Provider setup
Provider setup
ANTHROPIC_API_KEYset → provider =anthropicOPENAI_API_KEYset → provider =openaiOPENROUTER_API_KEYset → provider =openai(OpenRouter-compatible)
Custom models
Custom models
based_on tells Mycel which tokenizer to use. context_limit overrides auto-detection.Advanced MCP servers
Connect external services via the Model Context Protocol. MCP tools appear asmcp__{server_name}__{tool_name}.
- stdio (local process)
- HTTP (remote server)
- Local .mcp.json
Observation (tracing)
- Langfuse
- LangSmith
- Disabled
Environment variables
All string values in JSON config files support${VAR} expansion and ~ for home directory.