ZeroClaw reads all of its settings from a single TOML file atDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/openagen/zeroclaw/llms.txt
Use this file to discover all available pages before exploring further.
~/.zeroclaw/config.toml. This file is created for you when you run zeroclaw onboard, and the runtime logs the resolved path at INFO level on every startup. Once the file exists you can edit it by hand at any time — many fields are applied on the next inbound channel message without a restart.
Creating the config file
Run the onboarding wizard
~/.zeroclaw/config.toml with your provider, model, and API key already filled in. Pass --api-key, --provider, and --model to skip prompts.Config path resolution at startup follows this order:
ZEROCLAW_WORKSPACE environment variable, then the ~/.zeroclaw/active_workspace.toml marker file (if present), then the default ~/.zeroclaw/config.toml. You can also export the full JSON Schema with zeroclaw config schema.Top-level keys
These four keys sit at the root ofconfig.toml and control which provider, model, and temperature the agent uses by default.
API key for the selected provider. Overridden at runtime by the
ZEROCLAW_API_KEY or API_KEY environment variable. Store file: ~/.zeroclaw/auth-profiles.json when using subscription auth profiles.Provider ID or alias. Examples:
openrouter, anthropic, ollama, custom:https://your-api.com. See the Providers page for the full catalog.Model routed through the selected provider. The exact format depends on the provider (for example
anthropic/claude-sonnet-4-6 on OpenRouter, llama3.2 on Ollama).Sampling temperature for the model. Accepts values from
0.0 to 2.0. Values outside this range are rejected at parse time.Base URL override for the provider API. Required for remote Ollama, llama.cpp, vLLM, and custom endpoints.
Hot-reload fields
Whenzeroclaw channel start or zeroclaw daemon is already running, you do not need to restart the process to pick up changes to these fields. ZeroClaw re-reads them from config.toml on the next inbound channel message:
default_providerdefault_modeldefault_temperatureapi_keyapi_url- All
reliability.*keys
Complete config.toml example
The block below shows every top-level section with annotated defaults. You do not need all sections — omit any that you do not use.See also
Providers
Full provider catalog, custom endpoints, and subscription auth profiles.
Channels
Telegram, Discord, WhatsApp, and all other supported messaging channels.
Memory
SQLite, PostgreSQL, Lucid, and Markdown memory backends with embedding options.