TOPIC / RESOURCE

OpenClaw config templates: minimal to advanced

Six configuration templates for different complexity levels. Start with a minimal config, then add routing, budget control, and tuning as your needs grow.

Best for

  • 已经知道自己不需要一份"大而全"配置
  • 想先按极简、小团队、路由和预算四档选择复杂度
  • 希望从思路模板开始,而不是先抄一份过大的配置

Choose complexity first

Templates guide structure; match fields to your version.

Template 1: Minimal config

First run, single model, single channel.

{
  "goal": "Run the smallest working loop",
  "channel": "One real channel only",
  "model": "One stable model route",
  "skills": "Only skills needed for current task",
  "auth": "Set authentication explicitly",
  "budget": {
    "daily": 5,
    "monthly": 50
  }
}

Template 2: Small team config

Team collaboration, chat entry (Feishu, Slack), docs and message routing.

{
  "goal": "Stable team collaboration first",
  "channel": "Primary team chat entry",
  "model": "Most available stable route",
  "skills": ["document handling", "message reply", "structured output"],
  "safety": "Start with minimum permissions",
  "environments": ["dev", "staging", "prod"]
}

Template 3: Router config

Fallback, task separation. primary + fallback; routing.high_value_tasks → stronger model, routing.routine_tasks → cheaper; alert when fallback triggers.

Template 4: Budget control config

Cost concerns, long context, many tool calls.

{
  "budgetMode": "conservative",
  "limits": { "hourly": 100, "daily": 500, "monthly": 5000 }
}

Template 5: Caching and compaction

Long conversations, many tools. Enable promptCaching and compaction.mode: safeguard with a cheaper compression model.

Template 6: Multi-agent

Clear role split. Each Agent: own workspace and agentDir. Coordination: pass summaries, not full context.

Performance tuning

openclaw config set cache.enabled true
openclaw config set cache.ttl 3600
openclaw config set ai.maxConcurrentRequests 3
openclaw config set ai.timeout 30000
openclaw config set logging.level "debug"
openclaw logs

Priorities: cache on, cap concurrency/timeout, readable logs. Order: minimal → small team → router/budget only when needed.

External links

FAQ

Topic FAQ

Not always. Treat them as structure guides. Match fields to your version and environment.

Over-complexity on day one is the most common mistake. Layer templates by scenario, not by feature count.