Configuration Reference
Use this page when you need the field-level public config contract for Loong. If you want the shared shape first, start with Configuration Patterns.loong validate-config performs structural and range diagnostics for provider/channels/tools/memory/feishu_integration fields. Some fields (notably parts of conversation and most acp runtime knobs) are accepted and then normalized at runtime rather than rejected by validate diagnostics.
Configuration File Location
The default configuration file is located at:- Linux/macOS:
~/.loong/config.toml - Windows:
%USERPROFILE%\.loong\config.toml
~/.loongclaw/ homes are still discovered when ~/.loong/
has not been created yet, but the public path and examples in this reference
use the current ~/.loong/ home.
You can specify a custom path with the --config flag:
Configuration Sections
- top-level - Global selector and runtime state fields
- provider - LLM provider settings
- providers - Multiple provider profiles
- tools - Tool execution settings
- memory - Memory and conversation history
- conversation - Conversation runtime behavior
- acp - Agent Control Plane settings
- skills - External skill management
- audit - Audit logging
- channels - Channel-specific settings
- feishu_integration - Feishu OAuth integration settings
Validation Semantics
- Validate-config diagnostics: Fields that produce explicit validation diagnostics (error/warn) during
loong validate-config. - Runtime-normalized: Fields that are accepted at parse/validate time and clamped/defaulted by runtime resolution logic.
- Provider/runtime-dependent: Fields whose effective behavior depends on provider capability or runtime routing.
Valid Values / Range means the expected operational domain for that field.
top-level
Top-level fields that coordinate provider profile selection and runtime state.
Notes:
- In single-provider setups, the legacy
[provider]table can still be used. - In multi-provider setups,
[providers.<profile_id>]plusactive_provideris the canonical model.
provider
Configuration for the LLM provider.Provider Kinds
Example: OpenAI
Example: Kimi
Example: Local Ollama
providers
Map of named provider profiles for multi-provider configurations.
All fields from provider are available under each profile.
Example
tools
Configuration for tool execution and approval policies.
Notes:
toolsincludes strict numeric/domain diagnostics for browser/web/web_search/delegate child runtime limits.shell_default_modeis documented with supported operational values ("deny","allow").
tools.approval
tools.sessions
tools.messages
tools.delegate
tools.delegate.child_runtime.web
tools.delegate.child_runtime.browser
tools.browser
tools.web
tools.web_search
Example
memory
Configuration for conversation memory and history management.
Note:
memory.summary_max_chars values below 256 are accepted but normalized to an effective minimum of 256 at runtime.
Memory system notes:
- Normal operator-facing memory selection should stay on
memory.profile.memory.systemis an advanced/runtime-facing override, not the main public memory form. builtin: canonical SQLite-backed memory with structured retrieval planning and planner diagnostics.workspace_recall: workspace-document recall path optimized for retrieved references and rank-stage reordering.recall_first: provenance-aware recall path that suppresses summary context when retrieved memory is available.
Memory Profiles
Example
conversation
Configuration for conversation runtime behavior. Notes:- Several
conversationfields are runtime-normalized (for example clamped thresholds and minimum floors) instead of emitting validate-config errors.
Note:
conversation.tool_result_payload_summary_limit_chars is normalized to an effective runtime range of 256 to 64000.
conversation.turn_loop
Default Deny Markers
Default High-Risk Keywords
Example
acp
Configuration for Agent Control Plane (ACP). Notes:- ACP identifiers are normalized and checked when dispatch/session logic resolves them.
- Most ACP numeric controls are runtime-resolved (for example fallback to defaults when unset or non-positive) rather than validated as numeric-range diagnostics by
validate-config.
acp.dispatch
acp.backends.acpx
acp.backends.acpx.mcp_servers
Example
skills
Configuration for skills.Example
audit
Configuration for audit logging.Audit Modes
Example
channels
Configuration for input/output channels. Channel configuration uses top-level TOML tables such as[cli], [telegram], [feishu], and [matrix]; do not nest them under [channels.*].