Kilo Gateway 提供商集成设计
本文档描述了将 “Kilo Gateway” 作为 OpenClaw 中一等提供商集成的设计,以现有 OpenRouter 实现为模型。Kilo Gateway 使用 OpenAI 兼容的 completions API,但基础 URL 不同。
1. 提供商命名
Section titled “1. 提供商命名”推荐:kilocode
理由:
- 与提供的用户配置示例匹配(
kilocode提供商键) - 与现有提供商命名模式一致(例如
openrouter、opencode、moonshot) - 简短且易记
- 避免与通用的 “kilo” 或 “gateway” 术语混淆
考虑过的替代方案:kilo-gateway - 被拒绝,因为代码库中连字符名称不常见,且 kilocode 更简洁。
2. 默认模型引用
Section titled “2. 默认模型引用”推荐:kilocode/anthropic/claude-opus-4.6
理由:
- 基于用户配置示例
- Claude Opus 4.5 是一个能力出色的默认模型
- 显式模型选择避免了对自动路由的依赖
3. 基础 URL 配置
Section titled “3. 基础 URL 配置”推荐:硬编码默认值并支持配置覆盖
- 默认基础 URL:
https://api.kilo.ai/api/gateway/ - 可配置: 是,通过
models.providers.kilocode.baseUrl
这与其他提供商(如 Moonshot、Venice 和 Synthetic)使用的模式一致。
4. 模型扫描
Section titled “4. 模型扫描”推荐:初始阶段不提供专用模型扫描端点
理由:
- Kilo Gateway 代理到 OpenRouter,因此模型是动态的
- 用户可以在配置中手动配置模型
- 如果 Kilo Gateway 未来暴露
/models端点,可以添加扫描支持
5. 特殊处理
Section titled “5. 特殊处理”推荐:继承 Anthropic 模型的 OpenRouter 行为
由于 Kilo Gateway 代理到 OpenRouter,相同的特殊处理应适用:
anthropic/*模型的缓存 TTL 资格anthropic/*模型的额外参数(cacheControlTtl)- 转录策略遵循 OpenRouter 模式
需要修改的文件
Section titled “需要修改的文件”核心凭证管理
Section titled “核心凭证管理”1. src/commands/onboard-auth.credentials.ts
Section titled “1. src/commands/onboard-auth.credentials.ts”添加:
export const KILOCODE_DEFAULT_MODEL_REF = "kilocode/anthropic/claude-opus-4.6";
export async function setKilocodeApiKey(key: string, agentDir?: string) { upsertAuthProfile({ profileId: "kilocode:default", credential: { type: "api_key", provider: "kilocode", key, }, agentDir: resolveAuthAgentDir(agentDir), });}2. src/agents/model-auth.ts
Section titled “2. src/agents/model-auth.ts”在 resolveEnvApiKey() 的 envMap 中添加:
const envMap: Record<string, string> = { // ... existing entries kilocode: "KILOCODE_API_KEY",};3. src/config/io.ts
Section titled “3. src/config/io.ts”添加到 SHELL_ENV_EXPECTED_KEYS:
const SHELL_ENV_EXPECTED_KEYS = [ // ... existing entries "KILOCODE_API_KEY",];4. src/commands/onboard-auth.config-core.ts
Section titled “4. src/commands/onboard-auth.config-core.ts”添加新函数:
export const KILOCODE_BASE_URL = "https://api.kilo.ai/api/gateway/";
export function applyKilocodeProviderConfig(cfg: OpenClawConfig): OpenClawConfig { const models = { ...cfg.agents?.defaults?.models }; models[KILOCODE_DEFAULT_MODEL_REF] = { ...models[KILOCODE_DEFAULT_MODEL_REF], alias: models[KILOCODE_DEFAULT_MODEL_REF]?.alias ?? "Kilo Gateway", };
const providers = { ...cfg.models?.providers }; const existingProvider = providers.kilocode; const { apiKey: existingApiKey, ...existingProviderRest } = (existingProvider ?? {}) as Record< string, unknown > as { apiKey?: string }; const resolvedApiKey = typeof existingApiKey === "string" ? existingApiKey : undefined; const normalizedApiKey = resolvedApiKey?.trim();
providers.kilocode = { ...existingProviderRest, baseUrl: KILOCODE_BASE_URL, api: "openai-completions", ...(normalizedApiKey ? { apiKey: normalizedApiKey } : {}), };
return { ...cfg, agents: { ...cfg.agents, defaults: { ...cfg.agents?.defaults, models, }, }, models: { mode: cfg.models?.mode ?? "merge", providers, }, };}
export function applyKilocodeConfig(cfg: OpenClawConfig): OpenClawConfig { const next = applyKilocodeProviderConfig(cfg); const existingModel = next.agents?.defaults?.model; return { ...next, agents: { ...next.agents, defaults: { ...next.agents?.defaults, model: { ...(existingModel && "fallbacks" in (existingModel as Record<string, unknown>) ? { fallbacks: (existingModel as { fallbacks?: string[] }).fallbacks, } : undefined), primary: KILOCODE_DEFAULT_MODEL_REF, }, }, }, };}认证选择系统
Section titled “认证选择系统”5. src/commands/onboard-types.ts
Section titled “5. src/commands/onboard-types.ts”添加到 AuthChoice 类型:
export type AuthChoice = // ... existing choices "kilocode-api-key";// ...添加到 OnboardOptions:
export type OnboardOptions = { // ... existing options kilocodeApiKey?: string; // ...};6. src/commands/auth-choice-options.ts
Section titled “6. src/commands/auth-choice-options.ts”添加到 AuthChoiceGroupId:
export type AuthChoiceGroupId = // ... existing groups "kilocode";// ...添加到 AUTH_CHOICE_GROUP_DEFS:
{ value: "kilocode", label: "Kilo Gateway", hint: "API key (OpenRouter-compatible)", choices: ["kilocode-api-key"],},添加到 buildAuthChoiceOptions():
options.push({ value: "kilocode-api-key", label: "Kilo Gateway API key", hint: "OpenRouter-compatible gateway",});7. src/commands/auth-choice.preferred-provider.ts
Section titled “7. src/commands/auth-choice.preferred-provider.ts”添加映射:
const PREFERRED_PROVIDER_BY_AUTH_CHOICE: Partial<Record<AuthChoice, string>> = { // ... existing mappings "kilocode-api-key": "kilocode",};认证选择应用
Section titled “认证选择应用”8. src/commands/auth-choice.apply.api-providers.ts
Section titled “8. src/commands/auth-choice.apply.api-providers.ts”添加导入:
import { // ... existing imports applyKilocodeConfig, applyKilocodeProviderConfig, KILOCODE_DEFAULT_MODEL_REF, setKilocodeApiKey,} from "./onboard-auth.js";添加 kilocode-api-key 的处理:
if (authChoice === "kilocode-api-key") { const store = ensureAuthProfileStore(params.agentDir, { allowKeychainPrompt: false, }); const profileOrder = resolveAuthProfileOrder({ cfg: nextConfig, store, provider: "kilocode", }); const existingProfileId = profileOrder.find((profileId) => Boolean(store.profiles[profileId])); const existingCred = existingProfileId ? store.profiles[existingProfileId] : undefined; let profileId = "kilocode:default"; let mode: "api_key" | "oauth" | "token" = "api_key"; let hasCredential = false;
if (existingProfileId && existingCred?.type) { profileId = existingProfileId; mode = existingCred.type === "oauth" ? "oauth" : existingCred.type === "token" ? "token" : "api_key"; hasCredential = true; }
if (!hasCredential && params.opts?.token && params.opts?.tokenProvider === "kilocode") { await setKilocodeApiKey(normalizeApiKeyInput(params.opts.token), params.agentDir); hasCredential = true; }
if (!hasCredential) { const envKey = resolveEnvApiKey("kilocode"); if (envKey) { const useExisting = await params.prompter.confirm({ message: `Use existing KILOCODE_API_KEY (${envKey.source}, ${formatApiKeyPreview(envKey.apiKey)})?`, initialValue: true, }); if (useExisting) { await setKilocodeApiKey(envKey.apiKey, params.agentDir); hasCredential = true; } } }
if (!hasCredential) { const key = await params.prompter.text({ message: "Enter Kilo Gateway API key", validate: validateApiKeyInput, }); await setKilocodeApiKey(normalizeApiKeyInput(String(key)), params.agentDir); hasCredential = true; }
if (hasCredential) { nextConfig = applyAuthProfileConfig(nextConfig, { profileId, provider: "kilocode", mode, }); } { const applied = await applyDefaultModelChoice({ config: nextConfig, setDefaultModel: params.setDefaultModel, defaultModel: KILOCODE_DEFAULT_MODEL_REF, applyDefaultConfig: applyKilocodeConfig, applyProviderConfig: applyKilocodeProviderConfig, noteDefault: KILOCODE_DEFAULT_MODEL_REF, noteAgentModel, prompter: params.prompter, }); nextConfig = applied.config; agentModelOverride = applied.agentModelOverride ?? agentModelOverride; } return { config: nextConfig, agentModelOverride };}还需在函数顶部添加 tokenProvider 映射:
if (params.opts.tokenProvider === "kilocode") { authChoice = "kilocode-api-key";}CLI 注册
Section titled “CLI 注册”9. src/cli/program/register.onboard.ts
Section titled “9. src/cli/program/register.onboard.ts”添加 CLI 选项:
.option("--kilocode-api-key <key>", "Kilo Gateway API key")添加到 action 处理器:
kilocodeApiKey: opts.kilocodeApiKey as string | undefined,更新 auth-choice 帮助文本:
.option( "--auth-choice <choice>", "Auth: setup-token|token|chutes|openai-codex|openai-api-key|openrouter-api-key|kilocode-api-key|ai-gateway-api-key|...",)非交互式引导
Section titled “非交互式引导”10. src/commands/onboard-non-interactive/local/auth-choice.ts
Section titled “10. src/commands/onboard-non-interactive/local/auth-choice.ts”添加 kilocode-api-key 的处理:
if (authChoice === "kilocode-api-key") { const resolved = await resolveNonInteractiveApiKey({ provider: "kilocode", cfg: baseConfig, flagValue: opts.kilocodeApiKey, flagName: "--kilocode-api-key", envVar: "KILOCODE_API_KEY", }); await setKilocodeApiKey(resolved.apiKey, agentDir); nextConfig = applyAuthProfileConfig(nextConfig, { profileId: "kilocode:default", provider: "kilocode", mode: "api_key", }); // ... apply default model}11. src/commands/onboard-auth.ts
Section titled “11. src/commands/onboard-auth.ts”添加导出:
export { // ... existing exports applyKilocodeConfig, applyKilocodeProviderConfig, KILOCODE_BASE_URL,} from "./onboard-auth.config-core.js";
export { // ... existing exports KILOCODE_DEFAULT_MODEL_REF, setKilocodeApiKey,} from "./onboard-auth.credentials.js";特殊处理(可选)
Section titled “特殊处理(可选)”12. src/agents/pi-embedded-runner/cache-ttl.ts
Section titled “12. src/agents/pi-embedded-runner/cache-ttl.ts”添加 Kilo Gateway 对 Anthropic 模型的支持:
export function isCacheTtlEligibleProvider(provider: string, modelId: string): boolean { const normalizedProvider = provider.toLowerCase(); const normalizedModelId = modelId.toLowerCase(); if (normalizedProvider === "anthropic") return true; if (normalizedProvider === "openrouter" && normalizedModelId.startsWith("anthropic/")) return true; if (normalizedProvider === "kilocode" && normalizedModelId.startsWith("anthropic/")) return true; return false;}13. src/agents/transcript-policy.ts
Section titled “13. src/agents/transcript-policy.ts”添加 Kilo Gateway 处理(类似 OpenRouter):
const isKilocodeGemini = provider === "kilocode" && modelId.toLowerCase().includes("gemini");
// Include in needsNonImageSanitize checkconst needsNonImageSanitize = isGoogle || isAnthropic || isMistral || isOpenRouterGemini || isKilocodeGemini;用户配置示例
Section titled “用户配置示例”{ "models": { "mode": "merge", "providers": { "kilocode": { "baseUrl": "https://api.kilo.ai/api/gateway/", "apiKey": "xxxxx", "api": "openai-completions", "models": [ { "id": "anthropic/claude-opus-4.6", "name": "Anthropic: Claude Opus 4.6" }, { "id": "minimax/minimax-m2.5:free", "name": "Minimax: Minimax M2.5" } ] } } }}认证配置结构
Section titled “认证配置结构”{ "profiles": { "kilocode:default": { "type": "api_key", "provider": "kilocode", "key": "xxxxx" } }}测试注意事项
Section titled “测试注意事项”-
单元测试:
- 测试
setKilocodeApiKey()写入正确的配置文件 - 测试
applyKilocodeConfig()设置正确的默认值 - 测试
resolveEnvApiKey("kilocode")返回正确的环境变量
- 测试
-
集成测试:
- 测试
--auth-choice kilocode-api-key的引导流程 - 测试
--kilocode-api-key的非交互式引导 - 测试
kilocode/前缀的模型选择
- 测试
-
端到端测试:
- 测试通过 Kilo Gateway 的实际 API 调用(实时测试)
- 现有用户无需迁移
- 新用户可以立即使用
kilocode-api-key认证选择 - 现有手动配置的
kilocode提供商将继续工作
-
模型目录: 如果 Kilo Gateway 暴露
/models端点,添加类似scanOpenRouterModels()的扫描支持 -
OAuth 支持: 如果 Kilo Gateway 添加 OAuth,相应扩展认证系统
-
速率限制: 如需要,考虑添加 Kilo Gateway 特定的速率限制处理
-
文档: 在
docs/providers/kilocode.md添加说明设置和使用的文档
| 文件 | 变更类型 | 描述 |
|---|---|---|
src/commands/onboard-auth.credentials.ts | 新增 | KILOCODE_DEFAULT_MODEL_REF、setKilocodeApiKey() |
src/agents/model-auth.ts | 修改 | 向 envMap 添加 kilocode |
src/config/io.ts | 修改 | 向 shell 环境键添加 KILOCODE_API_KEY |
src/commands/onboard-auth.config-core.ts | 新增 | applyKilocodeProviderConfig()、applyKilocodeConfig() |
src/commands/onboard-types.ts | 修改 | 向 AuthChoice 添加 kilocode-api-key,向选项添加 kilocodeApiKey |
src/commands/auth-choice-options.ts | 修改 | 添加 kilocode 组和选项 |
src/commands/auth-choice.preferred-provider.ts | 修改 | 添加 kilocode-api-key 映射 |
src/commands/auth-choice.apply.api-providers.ts | 修改 | 添加 kilocode-api-key 处理 |
src/cli/program/register.onboard.ts | 修改 | 添加 --kilocode-api-key 选项 |
src/commands/onboard-non-interactive/local/auth-choice.ts | 修改 | 添加非交互式处理 |
src/commands/onboard-auth.ts | 修改 | 导出新函数 |
src/agents/pi-embedded-runner/cache-ttl.ts | 修改 | 添加 kilocode 支持 |
src/agents/transcript-policy.ts | 修改 | 添加 kilocode Gemini 处理 |