05. 配置管理对比：Crush vs Kimi Code CLI

5.1 配置文件格式

Crush: JSON

{
  "$schema": "https://charm.land/crush.json",
  "models": {
    "large": {"model": "claude-sonnet-4", "provider": "anthropic"},
    "small": {"model": "gpt-4o-mini", "provider": "openai"}
  },
  "providers": {
    "anthropic": {"type": "anthropic", "api_key": "$ANTHROPIC_API_KEY"}
  },
  "mcp": { "filesystem": {"type": "stdio", "command": "npx", ...} },
  "lsp": { "gopls": {"command": "gopls", "options": {...}} }
}

Kimi Code CLI: TOML

default_model = "kimi-for-coding"

[models.kimi-for-coding]
provider = "kimi"
model = "kimi-for-coding"
max_context_size = 128000

[providers.kimi]
type = "kimi"
api_key = "${KIMI_API_KEY}"

5.2 配置层级

Crush

1. 命令行参数 (最高)
2. .crush.json (项目)
3. crush.json (项目)
4. ~/.config/crush/crush.json (全局)
5. 默认值

Kimi Code CLI

1. 命令行参数 (最高)
2. 指定配置文件 (--config)
3. 项目配置 (<work_dir>/.kimi/)
4. 全局配置 (~/.kimi/)
5. 默认值

5.3 对比总结