Skip to main content
Mycel uses split configuration files for runtime defaults, models, observation, and provider-specific infrastructure. Product runtime state is not loaded from workspace-local runtime.json files.

Config file overview

JSON config files:
Other config files:
Runtime priority: explicit server/CLI overrides → built-in defaults. Merge strategy per domain:

First run

Export variables in the shell, or set ENV_FILE=/path/to/mycel.env before starting the service:

runtime.json

Pruning trims large tool results:Compaction summarizes old history via LLM when context fills:See Memory for full details.
Each tool group has an enabled flag. Both the group and individual tool must be enabled.
Complete tool catalog:
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.
explicit runtime overrides:

models.json

Mycel provides four leon:* aliases:Set via Settings → Models in the Web UI:
Override a mapping through Settings-backed model configuration:
Provider auto-detection (when no explicit provider is set):
  • ANTHROPIC_API_KEY set → provider = anthropic
  • OPENAI_API_KEY set → provider = openai
  • OPENROUTER_API_KEY set → provider = openai (OpenRouter-compatible)
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 as mcp__{server_name}__{tool_name}.

Observation (tracing)

Environment variables

All string values in JSON config files support ${VAR} expansion and ~ for home directory.