更新日志

版本发布说明与历史记录。

Changelog

All notable changes to krouter will be documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

[2.2.0] - 2026-05-23

Added

  • Daily budget hard stop: routing engine now checks DailyPercent >= 1.0 before selecting a provider. When the limit is reached, Decision.BudgetExceeded is set and the proxy returns HTTP 429 — Anthropic-protocol callers receive {"type":"error","error":{"type":"rate_limit_error",...}}, OpenAI-protocol callers receive {"error":{"type":"insufficient_quota",...}}. Requests are blocked until the spend counter resets at midnight UTC.
  • Budget monitor goroutine: monitorBudget runs a 60 s ticker in serve.go and broadcasts SSE events (budget_warning) at 80%, 95%, and 100% of the daily limit. Each threshold fires at most once per day (dedup via last-fired timestamp).
  • Dashboard budget bar: new BudgetBar component shows a live spend-vs-limit progress bar that turns yellow at 80%, red at 95%, and adds a "Blocked" badge with an unblock hint when spending is stopped.
  • Install wizard budget step: new BudgetStep page added between "Shell" and "Done". Defaults to $50/day; calls POST /api/install/set-budget on the install server so the limit is written to settings.json before the daemon starts for the first time.
  • Default $50/day limit: applyDefaults in internal/config/manager.go sets budget_warnings["daily"] = 50 when the key is absent, so out-of-the-box installs are protected without requiring the wizard step.
  • UI localization (English / Chinese): all user-visible strings in the dashboard and install wizard are extracted to frontend/src/locales/{en,zh}.json and frontend-install/src/locales/{en,zh}.json using react-i18next. Language is detected from navigator.language during install and from localStorage thereafter; the Settings page lets users switch at any time and syncs the choice to settings.json immediately.

Changed

  • GET /internal/budget response now includes daily_limit_usd, daily_percent_used, and budget_blocked when a daily limit is configured.
  • Currency display unified to USD across both English and Chinese locales — no per-locale currency formatting.

[2.1.0] - 2026-05-22

Fixed

  • Subscription routing could pick the wrong tier when minimax has multiple plans (spec/05 §8): subscriptionSource.GetSubscriptionInfo iterated GetAllSubscriptionQuotas and returned the first IsAvailable() row, then hardcoded the rewrite-target model as MiniMax-M2.7 regardless of which tier had matched. If a user's MiniMax-M* (LLM) tier was exhausted but speech-hd (TTS) still had quota, routing thought minimax was available, sent an LLM request as MiniMax-M2.7, and minimax replied 4xx because the M* tier was empty. Fixed by explicitly looking for the tier whose model_pattern wildcard-matches the rewrite target (storage.SubscriptionQuota.MatchesModel using path.Match). Standard tier preferred over highspeed; highspeed used only as fallback. New tests cover the speech-hd masking scenario, standard-vs-highspeed precedence, the highspeed fallback path, and the non-minimax provider case.

Added

  • subscription_exhausted SSE event (spec/05 §12.3): when the MiniMax quota poller observes a tier transitioning from "had quota" to "zero remaining" within the current window, the daemon broadcasts a subscription_exhausted event with {provider, tier, highspeed, window_end}. Dedupe key is window_end so we don't refire repeatedly within the same exhausted window. The dashboard SubscriptionQuotaCard listens for the event, surfaces a transient banner ("quota exhausted, routing fell back to per-token vendors until window reset at …"), and force-refetches /internal/subscription/status so the bars update immediately instead of waiting 60s for the next poll.

Changed

  • MiniMax subscription card now shows the original CNY price: the dashboard formerly displayed e.g. $6.76/mo plan, which felt odd to users who paid ¥49/月 on minimaxi.com. It now shows ¥49/mo (≈ $6.76). The USD value is still computed (CNY × 0.138 fixed rate) so users can compare costs against per-token vendors. New monthly_price_cny field on /internal/subscription/status carries the original number.
  • agentscan.PendingFileDir() now resolves to ~/.kinthai/ only (was: $XDG_CONFIG_HOME/krouter → ~/Library/Application Support/krouter → ~/.config/krouter fallback chain). This fixes a silent-data-loss bug where the installer running from a shell with XDG_CONFIG_HOME set would write pending-agents.json somewhere the launchd-started daemon never looks (LaunchAgent plists inject HOME but not arbitrary shell env vars). New regression test asserts the path is invariant under XDG_CONFIG_HOME changes. KROUTER_CONFIG_DIR continues to override (for tests and site-specific deployments).
  • GET /internal/agents is now a unified inheritance + legacy view (spec/04 §8.6): the existing JSON shape (name, connected, providers, stats) is preserved, but the response is now unioned with the Scanner registry plus agent_settings / inherited_endpoints so a dashboard refresh sees everything in one round-trip. New optional fields (all omitempty, so older clients ignore them): supported (Scanner compiled in for this agent), enabled (agent_settings.enabled), inherited_count, last_scanned_at, last_error. Scanner-registered agents that aren't yet installed on disk still appear (so the dashboard can show "OpenClaw (not installed)" rows); v2.0.47-style detection-only agents (Cursor / Hermes) still appear with supported=false until their Scanner ships.

Added

  • Auto-rescan + SSE on MiniMax OAuth failure (spec/05 §15.2): when the QuotaPoller sees the token rejected — either via HTTP 401/403 or via the body's base_resp.status_code = 1004 ("login fail") that the token-plan endpoint returns as HTTP 200 — it now invokes a registered UnauthorizedCallback. The daemon wires that callback to agentscan.RunAll (so any fresher OAuth token OpenClaw has written to auth-profiles.json since the last scan gets picked up automatically) and broadcasts a subscription_unauthorized SSE event so the dashboard can surface a "re-login OpenClaw" prompt if the rescan didn't help. New ErrMinimaxAuth sentinel error lets callers errors.Is(err, ErrMinimaxAuth) instead of parsing message strings.

Added

  • Periodic agent rescan (spec/04 §14 "Hot reload"): the daemon now runs agentscan.RunAll every 5 minutes in addition to the startup-time pass, so config changes the user makes to OpenClaw / Claude Code between daemon restarts are picked up without manual intervention. After each tick the daemon broadcasts an agents_changed SSE event with source: periodic_rescan so the dashboard can refetch /internal/agents/configured immediately rather than waiting for its own react-query refetch interval. Implemented as agentscan.StartPeriodicRescan(ctx, store, logger, interval, onTick) — exported so tests (and future fsnotify variants) can drive it with a custom cadence.

Added

  • spec/00-design-principles.md: distilled cross-cutting design rules (product positioning, transparent-proxy invariants, data architecture, UX rules, engineering trade-offs, process meta-rules). New PRs and reviews are expected to reference principles by their letter+number (e.g. "violates C2 — single source of truth"). Compiled from the working-session history that produced spec/04 and spec/05; each principle ships with the concrete incident or trade-off that motivated it, so a future contributor can decide whether the rule still applies when their case looks different.

Added

  • Agent inheritance flow (spec/04): krouter now auto-extracts vendor endpoints, API keys, and OAuth tokens from the user's already-configured AI agents (OpenClaw, Claude Code) and persists them to a new inherited_endpoints table. Wizard gains an "Agent Paths" step; Dashboard gains an inheritance section. See spec/04-agent-inheritance.md.
  • Subscription quota dashboard (spec/05): new /internal/subscription/status and /internal/subscription/refresh endpoints; Dashboard gains a MiniMax subscription card showing effective cost, monthly price, and per-tier window-reset countdown. See spec/05-subscription-quota.md.
  • Scanner architecture (internal/agentscan): one Go file per AI agent implementing the Scanner interface (AgentID, DisplayName, DefaultConfigPath, Scan). Adding a new agent is purely additive — write the file, append the value to the registry — no schema change, no manifest layer.
  • Injectable MiniMax QuotaPoller.WithTokenResolver: the poller now reads the OAuth token from inherited_endpoints.extras_json first, closing the cold-start gap where the daemon couldn't poll quota until the user had sent a first proxied MiniMax request.
  • resolveProviderKey helper: routing engine and model discovery resolve vendor API keys through a single helper with precedence inherited_endpoints > settings.ProviderKeys > env var. Vendors the user already configured in OpenClaw no longer require a second key entry in the dashboard Settings page.

Fixed

  • MiniMax pricing — duplicate tables disagreed (caught in PR review): an earlier commit in this PR introduced internal/providers/minimax/pricing.go as an independent lookup table (USD prices, formula monthly_price_usd / total_count) that conflicted with the existing internal/storage/subscription_quota.go::minimaxPlanPriceCNY (CNY prices, formula multiplied by windows_per_month). Worst case: the dashboard reported an effective cost roughly 1043× the value the routing engine was using; the SKU {600, true} was treated as "free" by routing while the dashboard quoted $0.0483/call. Fix: deleted internal/providers/minimax/pricing.go outright, routed all callers through storage.SubscriptionQuota.EffectiveCostUSD() and MonthlyPriceUSD() (single source of truth), corrected the spec/05 §11 formula to include the windows_per_month factor, and added the pricing matrix + call graph + bug history to the spec as a cautionary note for future contributors.

[2.0.50] - 2026-05-19

Added

  • 数据驱动 Provider 架构：新增 provider_config DB 表（migration 007），预置 15 个 provider 的元数据（name、display_name、base_url、path_prefix、protocol、is_builtin）。daemon 启动时从 DB 加载所有 OpenAI 兼容 provider，不再需要修改代码才能支持新 provider。
  • 新增 7 个内置 provider：Google Gemini（/v1beta/openai 兼容端点）、xAI Grok、Mistral AI、Together AI、Fireworks AI、Perplexity、Ollama（本地）。加上现有 8 个，总计 15 个内置 provider，均通过 API key 配置即可激活。
  • 自定义 provider CRUD：POST /internal/providers（创建自定义 provider）、DELETE /internal/providers/:name（删除自定义 provider）。支持热添加/删除，无需重启 daemon。
  • Providers 页面 UI 升级：显示 display_name 和 base_url（来自 DB），"Add Provider"对话框支持填写 name/base_url/api_key/path_prefix/protocol 添加任意 OpenAI 兼容端点；每个未配置 provider 卡片内联"Set Key"输入框，可直接在 Providers 页设置 API key；自定义 provider 显示删除按钮。
  • provider_keys 校验放开：PATCH /internal/settings 的 provider_keys 从静态白名单改为格式校验（小写字母开头 + 字母数字 + -_），允许为任意 provider 设置 key。
  • LiteLLM 映射扩展：LiteLLMToKrouterProvider 新增 together_ai→together、fireworks_ai→fireworks，LiteLLM 同步的模型定价可自动关联到对应 provider。

Changed

  • serve.go 移除了 deepseek、groq、moonshot、glm、qwen、openai 六个硬编码适配器注册，改为 loadProvidersFromDB() 统一加载。现有 per-provider 包（用于测试和文档）保持不变。
  • GET /internal/providers 响应新增 display_name、base_url、is_builtin 字段。

[2.0.49] - 2026-05-19

Fixed

  • Bug F（P1）— Claude streaming token 永远 0 — 根因修复：Anthropic API 对发送了 Accept-Encoding: gzip 的请求返回 gzip 压缩响应；krouter 直接把压缩字节写入 SSE capture buffer，parseAnthropicSSEUsage 永远解析失败。修复：在 Anthropic 适配器的 Forward 方法里删除上游请求的 Accept-Encoding 头，强制返回未压缩文本。代价：每次响应多几 KB 流量，换取 token 统计可靠性。
  • Bug Q — installer 端口 8404 静默切换：stopRunningDaemon() 只停 daemon service，不杀残留的老 installer 进程；老 installer 占用 8404 时新 installer 静默切到 8405，用户/脚本基于固定端口假设的操作全部 noop。修复：启动前新增 stopRunningInstaller(8404) — 先 TCP 探测端口是否占用，若占用则用系统命令（macOS: lsof -ti | xargs kill -9，Linux: fuser -k，Windows: netstat + taskkill）强制杀掉。

[2.0.48] - 2026-05-19

Fixed

  • Bug P（P0）— migration 005 UNIQUE 冲突致 daemon 启动失败：005_rename_glm_to_zai.sql 在 glm 和 zai 行并存时触发 UNIQUE constraint failed，daemon 无法启动。修复：先删除与已有 zai 行冲突的 glm 行，再执行 UPDATE；对已完成 migration 的 DB 无影响（schema_migrations 版本记录存在则跳过）。

Added

  • Bug F 诊断工具：proxy 层在每次 Anthropic 流式响应结束后，将 SSE raw buffer（最多 4 KB）存入 Server.lastSSECapture；当 parseAnthropicSSEUsage 返回 0/0 token 时，debug 日志打印前 512 字节供排查。新增 GET /internal/debug/last-sse-capture（需 Bearer auth）端点，返回上次捕获的原始 SSE bytes，方便研发判断流内容是否包含 message_start / message_delta 事件。

[2.0.47] - 2026-05-19

Added

  • Dashboard 周报统计：新增 GET /internal/dashboard/stats 端点，返回近 7 天请求数、花费、节省金额、provider 分布及已连接 agent 数量；Dashboard 页面新增"This Week"汇总卡片和 provider 分布饼图（recharts）。
  • Provider 今日统计：GET /internal/providers 响应新增 requests_today、cost_today_usd、latency_p50_ms、latency_p95_ms 字段，Providers 页面展示今日请求量和延迟百分位。
  • Provider Test 按钮：新增 POST /internal/providers/{name}/test 端点，向 provider 发起轻量连通性探测（Anthropic 测 API 可达性，OpenAI-compatible 测 key 有效性）；Providers 页面每个卡片增加 Test 按钮，实时显示延迟和 HTTP 状态码。
  • Agent 配置 diff 预览：新增 POST /internal/agents/{name}/diff 端点，返回 connect 前后的配置 JSON diff（不写文件）；Agents 页面在 OpenClaw 点击 Connect 时先弹出 before/after 对比模态框，确认后再执行。
  • Agent 备份管理：新增 GET /internal/agents/{name}/backups 和 POST /internal/agents/{name}/restore 端点；Agents 页面每个已知 config-path 的 agent 卡片底部增加可折叠"Backups"面板，列出所有备份并支持一键还原。
  • 日志日期范围过滤：GET /internal/logs 新增 ?from=YYYY-MM-DD&to=YYYY-MM-DD 参数；Logs 页面新增两个日期选择器，设置后按范围过滤记录。
  • 日志 CSV 导出接口：新增 GET /internal/logs/export?from=&to= 端点，返回 CSV 文件下载；Settings 页面新增日期范围输入 + Export CSV 链接。
  • 数据管理：新增 POST /internal/settings/reset-data（清空请求历史）、POST /internal/settings/uninstall（断开所有 agent 连接）；Settings 页面新增"Data Management"分区含上述两个操作按钮。
  • 通知类别扩展：HandleEvent 新增四种通知类型：free_credit（免费额度到账）、provider_news（provider 更新）、tip（节省建议）、critical_warning（严重告警）；Settings 页面通知偏好列表同步补全这四项。
  • Pinger 接口：providers 包新增 Pinger 可选接口；Anthropic 和 OpenAI 适配器各实现 Ping(ctx) (latencyMS, statusCode, err) 方法。

[2.0.46] - 2026-05-19

Added

  • 5xx Fallback 链：proxy 层新增 tryWithFallback，当 provider 返回 5xx 或网络错误时自动调用 engine.FallbackDecide，最多重试 2 次；Anthropic 协议按 opus→sonnet→haiku 降档，OpenAI 协议切换到其他同协议 provider；4xx（401/429）直接透传，不触发重试。
  • 复杂度评分（ComplexityScore）：替换原来的布尔判断（HasImages || HasTools && tokens>4000），综合图片、大 token 量、HasTools 组合、system prompt 关键词（debug / refactor / architect 等 10 个）计算 0.0~1.0 分值；Quality preset 以 ≥0.4 为复杂请求阈值，决定是否升级到 Opus。
  • EstimatedCostUSD 填充：enrichDecision 在 routing engine 内部自动计算路由决策的预估花费，填入 Decision.EstimatedCostUSD；当路由模型比请求模型便宜时，在 Reason 末尾追加"比 X 便宜 Y%"。
  • per-agent 路由覆盖：settings.json 新增 routing_overrides 字段，支持按 agent 名（openclaw / claude-code / cursor / unknown）配置 always_use（强制使用特定模型）或 preset（覆盖活跃 preset）；engine 通过新增的 OverrideSource 接口注入，daemon 启动时由 config.Manager 实现。

[2.0.45] - 2026-05-19

Added

  • 请求元数据提取（HasImages / SystemPrompt）：proxy 层在构建 routing.Request 前调用 extractAnthropicMeta / extractOpenAIMeta，解析请求体中的 system 字段和图片内容块，填充 HasImages、SystemPrompt 字段。路由引擎可据此在订阅优先路由时跳过含图片请求（MiniMax 不支持）。
  • Anthropic 预算限制自动降级：routing engine 新增 QuotaSource 接口和 applyQuotaDowngrade 逻辑；当每日/每周花费占比 ≥ 95% 时强制切换 Saver preset，≥ 80% 时将 Quality→Balanced、Balanced→Saver；OpusPercent（基于 500K token 软上限的窗口消耗比）≥ 80% 时屏蔽 Opus 系列，降级使用 Sonnet。
  • QuotaSource / SubscriptionSource 接口：routing engine 通过 WithQuota(QuotaSource) 和 WithSubscription(SubscriptionSource) 注入依赖，保持路由层与存储层解耦，便于测试替换。

[2.0.44] - 2026-05-19

Added

  • MiniMax 订阅 provider 优先路由：routing engine 新增 SubscriptionSource 接口，当 MiniMax 订阅配额有剩余且请求不含图片时，三个 preset（Saver / Balanced / Quality 非复杂）均优先路由到 MiniMax，利用"月费÷月总次数"极低的有效成本（≈$0.000031/次）覆盖大多数请求。
  • MiniMax 配额轮询（QuotaPoller）：每 30 分钟调用 https://api.minimaxi.com/v1/token_plan/remains，当前窗口剩余 < 30 分钟时缩短为 5 分钟；结果存入新 DB 表 subscription_quota_cache；daemon 启动后 20 秒触发首次拉取。
  • OAuth token 缓存：proxy 在每次 MiniMax 请求中提取 Authorization: Bearer 头并存入内存（minimax.CacheOAuthToken），供 QuotaPoller 调用配额 API 时使用；token 不写磁盘、不打印日志。
  • SubscriptionQuota 存储层：新增 internal/storage/subscription_quota.go，包含 UpsertSubscriptionQuota、GetSubscriptionQuota、GetAllSubscriptionQuotas、IsSubscriptionAvailable 方法；EffectiveCostUSD() 按订阅套餐价格表计算每次调用等效美元成本。
  • DB migration 006_subscription_quota.sql：创建 subscription_quota_cache 表。

[2.0.43] - 2026-05-19

Fixed

  • Bug F（Anthropic streaming token 为 0）：parseAnthropicSSEUsage 和 parseAnthropicJSONUsage 改用 JSON 解析替代正则表达式，累加 input_tokens + cache_creation_input_tokens + cache_read_input_tokens 作为总 input token 数，修复了 prompt caching 激活时 input_tokens 字段为 0 导致统计清零的问题。cache_read_input_tokens 作为 cachedTokens 传入定价函数，享受折扣费率。
  • Bug O（glm→zai 重命名遗漏）：新增 DB migration 005_rename_glm_to_zai.sql，将 model_discovery 表中旧的 provider='glm' 行批量改为 'zai'；新增 config.Manager.MigrateKeys() 在 daemon 启动时自动将 settings.json 中的 provider_keys.glm 迁移为 provider_keys.zai，避免老版本升级后 API key 失效。
  • Bug L（settings 接受未知 vendor）：PATCH /internal/settings 的 provider_keys 字段现在校验 key 是否合法（deepseek / groq / moonshot / zai / qwen / openai / minimax），传入未知 key 时返回 400 Bad Request，附带可接受 key 列表。

Added

  • Bug K（OpenAI 直连 provider）：注册 openai provider（https://api.openai.com，OPENAI_API_KEY），支持 gpt-4o、gpt-4o-mini、gpt-4-turbo、gpt-4、o1、o1-mini、o3-mini。兑现 README 承诺。

[2.0.42] - 2026-05-19

Added

  • 全量模型 Catalog（model_catalog 表）：LiteLLM JSON 每 24h 同步时，将所有模型条目（含 cost=0 的）写入新的 model_catalog 表，字段包括 litellm_provider、model_id（去掉 provider 前缀）、raw_key、定价与 max_tokens。此表作为全平台大模型目录的权威来源。
  • pricing.LiteLLMToKrouterProvider 映射表：声明 LiteLLM provider 名称与 krouter adapter 名称不同的对应关系（目前仅 dashscope → qwen；其余在两侧名字一致后直接对应）。
  • providers.ModelSetter 接口：允许在运行时替换 adapter 的 SupportedModels() 列表。anthropic 和 openai（含所有 OpenAI-compatible 子适配器）均实现此接口。
  • pricing.Service.OnSync 回调：每次 LiteLLM 同步完成后调用，传入按 litellm_provider 分组的模型列表。serve.go 注册此回调，自动将 catalog 模型列表推送到对应 adapter，无需重启 daemon。
  • 新 DB migration 004_model_catalog.sql：创建 model_catalog 表及 idx_model_catalog_provider 索引。
  • storage.Store.UpsertModelCatalogBatch / GetModelsByLiteLLMProvider / GetAllModelCatalog：新增 catalog 相关 storage 方法。

Changed

  • GLM adapter 改名 glm → zai：跟进智谱品牌重命名（Z.AI），与 LiteLLM 和 OpenClaw 命名保持一致。settings key 同步改为 zai（旧配置需手动更新 ZHIPU_API_KEY 对应的 settings 键名）。静态模型列表补充新版 glm-4.5 系列。
  • Moonshot adapter 改名 moonshot-cn → moonshot：与 LiteLLM 和 OpenClaw 命名保持一致。静态模型列表补充新版 Kimi 系列（kimi-k2.5、kimi-k2.6、kimi-latest 等），保留旧版 moonshot-v1-* 作为 fallback。

[2.0.41] - 2026-05-19

Added

  • Settings → Pricing 页面（spec/04-pricing.md §8）：Settings 页面新增 Pricing Data 区块，展示：
    • 最近同步时间、数据来源徽标（live / cache / static）、已追踪模型数量
    • 本月总花费与节省金额（micro-USD 精度）
    • 过去 30 天 Top 10 模型使用表格（请求数、花费、输入/输出每百万 token 价格）
  • GET /internal/pricing/status 管理 API 端点：返回同步元信息、模型统计、本月聚合花费及 30 天热门模型列表。
  • pricing.Service.ModelCount() int：返回当前内存价格表中的模型数量，供 API 层展示。
  • pricing.Service.PriceFor(model string) (inputPerMTok, outputPerMTok float64)：按模型返回每百万 token 的输入/输出价格，便于前端展示不做单位换算。
  • storage.Store.TopModelsByUsage(ctx, since, limit)：按请求数降序汇总指定时间窗口内的模型使用统计。
  • storage.Store.ListRequestsSince(ctx, since, limit)：按时间段查询请求记录，用于月度节省计算。

[2.0.40] - 2026-05-19

Added

  • 价格 tier 驱动路由（spec/04-pricing.md §5）：routing engine 现在通过 WithPricing(PricingSource) 接收 live 价格数据，在 Saver / Quality preset 下动态选择最便宜/最贵的 (provider, model) 对，不再依赖硬编码模型名。
    • Saver preset：cheapestProviderModel 遍历所有健康且有 key 的同协议 provider，按 InputCostPerToken 选最低价模型。若 DeepSeek 比当前注册的 OpenAI gpt-4o-mini 更便宜，saver 自动选 DeepSeek。
    • Quality preset（复杂请求）：mostExpensiveProviderModel 选最贵模型作为能力最强的升级目标，代替硬编码 claude-opus-4-5。
    • 向下兼容：pricing 未注入（nil）或模型不在价格表时，自动回退到原有硬编码逻辑，现有行为不变。
  • pricing.Service.InputCostPerToken(model string) float64：新增公开方法，供 routing engine 按模型查询价格，无需构造完整 token 计数。
  • routing.PricingSource 接口：仅暴露 InputCostPerToken，最小化 routing → pricing 的依赖，便于测试时替换。

[2.0.39] - 2026-05-19

Fixed

  • pricing: 同步请求不走 OS 代理：pricing.Service 之前用硬编码 &http.Client{} 访问 raw.githubusercontent.com，在国内受限网络下每 24h 同步必超时。新增 WithHTTPClient(*http.Client) *Service 方法；serve.go 在创建 bgTransport（与 notifications/upgrade 共享的代理感知 transport）后立即注入，然后才调用 StartSync。
  • pricing: raw_json 列有 schema 但从不写入：syncOnce 写 UpsertPrice 时缺失 RawJSON 字段，导致 pricing_cache.raw_json 始终为空字符串，无法用于调试。修复：parseLiteLLM 返回内部 parsedEntry{PriceEntry, RawJSON} 结构，将原始 JSON bytes 一并传到 UpsertPrice；内存价格表（prices map）仍只保存 PriceEntry，内存占用不变。

[2.0.38] - 2026-05-19

Fixed

  • Bug H — 首次安装用户 anthropic.models=[]：RefreshModelsIfStale（daemon 启动 +10s 执行）之前只处理 settings 里有 key 的 provider，跳过了 Anthropic（key 在 openclaw.json 里，不在 krouter settings 里）。修复：RefreshModelsIfStale 现在也会检查 OpenClaw 是否已连接，若 anthropic 缓存为空或超过 24h，则调用 discoverOpenClawModels，首次安装用户的模型选择器将在 daemon 启动约 10s 后自动填充。
  • Bug I — minimax-portal.models 永远 []：discoverOpenClawModels 之前只处理 anthropic provider，从不更新 OpenClaw 的 minimax-portal 节点。修复：新增 discoverOpenClawMiniMax，若 OpenClaw 配置中存在 minimax-portal 节点则自动写入模型列表——优先通过 minimax-portal.apiKey 做实时探测，若 key 不存在则写入 adapter 的静态模型列表（MiniMax-M2.7、MiniMax-M2.7-highspeed），确保 model selector 始终非空。同时新增 ReadOpenClawProviderAPIKey(configPath, providerName) 通用函数（ReadOpenClawAPIKey 成为其包装）。
  • Bug J — daemon 内部服务（announcements/upgrade）不走 OS 系统代理：notifications.Service 和 upgrade.Service 各自创建了硬编码 &http.Client{}，不使用 proxycfg.Manager 探测的代理，导致国际网络受限环境下持续 timeout。修复：两个 service 新增 WithHTTPClient(*http.Client) *Service 方法，serve.go 在 daemon 启动时注入共享的代理感知 transport（Proxy: proxymgr.ProxyFunc()），upgrade 15s 超时、notifications 30s 超时，均通过 proxymgr.ProxyFunc() 闭包自动感知代理变更。

[2.0.37] - 2026-05-19

Fixed

  • Bug G — Saver preset 在多 provider 环境下误路由到 MiniMax：当同时注册了 Anthropic 和 MiniMax（均使用 Anthropic 协议）时，decideSaver 之前调用 pickHealthyProvider 可能返回 MiniMax，再把 claude-haiku-4-5-20251001 这个 Claude model ID 发给它——MiniMax 不识别该 ID，请求静默失败。修复：改用 pickProviderForModel(proto, saverAnthropicModel)，优先选择在 SupportedModels() 中明确列出该 haiku 型号的 provider；若回退 provider 不支持该型号，保持原始请求 model 不变。
  • Bug F — Anthropic streaming 请求 latency 统计错误（总是显示 6ms）：streamSSEWithCapture 的 done 回调之前会传入自身内部计时的 latencyMS，该计时在首字节已到达后才开始，导致记录的永远是流写入耗时（≈6ms）而非真实端到端延迟（如 7000ms）。修复：移除 done 回调中的 latencyMS 参数，两处调用处改为 time.Since(start) 计算从请求到达时刻起的完整延迟。
  • Bug F — Anthropic streaming token 捕获失败（长响应丢失 message_delta）：之前只保留头部 256KB，对于超过此大小的长响应，末尾的 message_delta（含 output_tokens）会被丢弃，导致 token 统计 output=0、cost=0。修复：改为 64KB 头部缓冲区 + 4KB 尾部滑动窗口，始终保留响应末尾内容，确保 message_delta 不丢失，同时大幅降低内存占用。

[2.0.36] - 2026-05-19

Added

  • Model Discovery：krouter 现在会在用户连接 OpenClaw 后自动探测可用模型列表。连接时读取 OpenClaw 配置里的 Anthropic API key，调用 /v1/models 接口，将返回的模型列表写入 OpenClaw 的 models.providers.anthropic.models 字段，使 OpenClaw 的模型选择器立即呈现真实可用的模型。所有已发现模型同时缓存到本地 SQLite DB（model_discovery 表）。
  • OpenAI-compatible provider 模型探测：daemon 启动 10s 后自动检查 settings 里有 key 的 provider（DeepSeek、Groq 等），若缓存超过 24h 则重新探测并更新 DB。
  • 新端点 GET /internal/models：返回 DB 中所有已发现模型，按 provider 分组。
  • 新端点 POST /internal/models/refresh：手动触发全量刷新（settings-keyed providers + 已连接的 OpenClaw Anthropic key），异步执行，立即返回 {"ok":true}。
  • ModelDiscoverer 可选接口：Anthropic 和 OpenAI adapter 均已实现，支持通过 keyFn 透传 API key，不暴露给 krouter 存储层。OpenAI adapter 的 modelsEndpointURL() 正确处理 GLM（/v4/models）和 Qwen（/compatible-mode/v1/models）的 pathReplace。

[2.0.35] - 2026-05-19

Added

  • HTTP proxy 支持（OS 系统代理 + per-provider bypass）：daemon 现在像 Chrome 一样自动读取 OS 系统代理设置（macOS scutil --proxy、Windows 注册表 HKCU\Internet Settings、Linux GNOME gsettings），无需用户在 krouter 里单独配置代理。国内直连 provider（MiniMax、Moonshot、DeepSeek、GLM/Zhipu、Qwen）通过内置 no-proxy 后缀列表绕过代理，Anthropic/Groq 等国际 provider 走代理。代理检测每 60s 刷新一次，VPN 接入/断开后自动生效。
  • 新端点字段：GET /internal/status 响应新增 proxy 字段（{"url":"","source":"none","active":false}），未来 Web UI 可在 Providers 页面展示当前代理状态。

[2.0.34] - 2026-05-18

Changed

  • Web UI 认证简化：废弃 session cookie + ticket-exchange 方案，改为基于 Origin header 的 CSRF 防护。认证中间件决策顺序：① 有效 Bearer token → 无条件放行（CLI / 程序化访问）；② Origin 存在且不等于 http://127.0.0.1:8403 → 403（跨域拦截，防 CSRF）；③ 无 Origin 或正确 Origin → 放行（curl / 浏览器 dashboard）。浏览器访问 dashboard 不再需要任何登录流程，daemon 重启也不影响体验。
  • 删除端点：POST /internal/auth/ticket、GET /internal/auth/exchange 已移除
  • install server 简化：handleDaemonReady 不再 mint ticket，直接返回 redirect_url: /krouter/；移除 readInternalTokenFn / mintDaemonTicketFn 依赖

Security

  • 安全性等效：Origin header 由浏览器自动设置且不可被跨域 JS 伪造（W3C CORS 规范强制）；curl / CLI 不发 Origin，不受影响；有效 Bearer token 可绕过 CSRF 检查（持有 token 即已认证）

[2.0.33] - 2026-05-18

Fixed

  • Bug D — defaultOpenClawModels 格式错误：之前注入的是字符串数组（如 ["claude-opus-4-5", ...]），但 OpenClaw ModelDefinitionSchema 要求每个元素是对象（{id, name, ...}），全新机器首次运行 krouter connect openclaw 时 OpenClaw 会 schema validation crash。改为注入空数组 []：空数组满足 z.array(ModelDefinitionSchema) schema、不会 crash；OpenClaw 通过 plugin 系统动态加载模型目录，不依赖该字段内容

[2.0.32] - 2026-05-18

Fixed

  • MiniMax 请求计费：MiniMax-M2.7 和 MiniMax-M2.7-highspeed 加入静态价格表（LiteLLM 目前未收录 MiniMax 模型，导致 cost_micro_usd = 0）。价格来源：MiniMax API 平台（$0.30/1M input、$1.20/1M output）
  • Savings 误算：当 cost_micro_usd = 0（未知模型价格，非真正免费）时，savings 会被错误地计为 baseline - 0 = baseline。现在仅在实际费用 > 0 时才计算 savings，影响 /internal/budget 和 /internal/usage 两个端点
  • OpenClaw agent 识别：OpenClaw 使用 Anthropic TypeScript SDK，其 User-Agent 为 Anthropic/JS X.Y.Z，不含 "openclaw" 字符串，导致 agent = "unknown"。新增通过 anthropic-dangerous-direct-browser-access: true 请求头识别 OpenClaw（该 header 由 OpenClaw SDK client 在所有 Anthropic provider 请求中注入，Claude Code CLI 不发送此 header）
  • per-agent 统计：随 agent 识别修复自动生效，OpenClaw 请求将正确计入 openclaw 分组

[2.0.31] - 2026-05-18

Fixed

  • MiniMax-portal OAuth 透传：v2.0.30 错误地将 MiniMax adapter 改成 Bearer key 注入模式。MiniMax-portal 的认证由 OpenClaw 的 OAuth 流程生成（从 auth-profiles.json 读取 access token），krouter 不应注入任何 key，应完整透传 OpenClaw 生成的 Authorization header。MiniMax adapter 恢复为 Anthropic 协议透明代理，upstream 端点更新为正确的 https://api.minimaxi.com/anthropic（portal API，区别于 chat API api.minimax.chat）
  • ConnectOpenClaw 新增 minimax-portal 支持：若用户 openclaw.json 中有 minimax-portal provider（含 authHeader: true OAuth 配置），connect 时自动将其 baseUrl 重定向到 krouter；disconnect 时恢复为 https://api.minimaxi.com/anthropic/v1。OAuth 凭证（authHeader、models、access token 等）全程不接触

Architecture note

MiniMax-portal 的完整流程：

  1. OpenClaw → krouter:8402（OpenClaw OAuth 流程注入 Authorization header）
  2. krouter → https://api.minimaxi.com/anthropic/v1/messages（透明代理，保留原始 header）

[2.0.30] - 2026-05-18

Fixed

  • LaunchAgent 无 EnvironmentVariables：plist 新增 EnvironmentVariables 段，注入扩展 PATH（含 ~/.claude/local、~/.local/bin、~/go/bin、/opt/homebrew/bin、/usr/local/bin）和 HOME，彻底解决 daemon 作为 LaunchAgent 运行时工具不可见的问题
  • Provider 注册依赖 shell env：所有 secondary provider（DeepSeek / Groq / Moonshot / GLM / Qwen / MiniMax）改为始终注册；API key 通过 keyFn 在每次请求时动态读取，优先读 ~/.kinthai/settings.json 的 provider_keys，再 fallback 到环境变量。LaunchAgent 无 shell env 时仍可通过 settings.json 配置 key
  • Providers 页只显示 anthropic：GET /internal/providers 新增 configured: bool 字段；有 key 的 provider 显示为 "Active"，无 key 的显示为 "Not configured"（不再从注册表缺失，始终可见）
  • Claude Code 在 Agents 页永远空：DetectInstalledAgents 在 exec.LookPath("claude") 失败后改为搜索已知路径（~/.claude/local/claude、~/.local/bin/claude、/usr/local/bin/claude、/opt/homebrew/bin/claude），LaunchAgent 最小 PATH 下也能找到
  • MiniMax adapter 从 Anthropic 透明代理改为 OpenAI Bearer-auth 方式，key 注入逻辑与其他 secondary provider 一致

Added

  • Settings.ProviderKeys map[string]string：存储 secondary provider 的 API key，存入 ~/.kinthai/settings.json（0600 权限）；PATCH /internal/settings 支持 provider_keys 字段（空字符串 = 删除该 key）
  • providers.Configurable 可选接口：HasKey() bool，由 openai.Adapter 实现；透明代理（Anthropic）不实现，默认视为已配置
  • openaiAdapter.NewWithKeyFn / NewWithPathReplaceAndKeyFn：接受 func() string 的 key getter，替代硬编码环境变量名
  • 所有 secondary adapter（deepseek / groq / moonshot / glm / qwen / minimax）加 NewWithKeyFn 构造函数
  • Providers 页 "Not configured" 卡片 hint 更新为同时提示 env var 和 settings.json 两种配置方式

[2.0.29] - 2026-05-18

Fixed

  • OpenClaw connect 后仍 crash-loop（Bug C）：ConnectOpenClaw 写入配置时未设置 models.providers.anthropic.models 字段，但 OpenClaw schema 强校验该字段必须为非空数组，导致 OpenClaw 启动即崩溃。现在连接时若 models 字段缺失，自动注入当前生产 Claude 模型列表；用户已有的自定义 models 列表不覆盖
  • DisconnectOpenClaw 遗留垃圾节点：旧 krouter 版本断开后会在 models.providers 下残留空的或仅有 models 字段的 anthropic 对象。现在：若断开后 provider 中不存在真实 apiKey，说明该 anthropic section 完全由 krouter 创建，一并清除（包括 krouter 注入的 models 数组和空节点）
  • 完善 TestDisconnectOpenClaw_RemovesOldPlaceholderApiKey：占位符 apiKey 被移除后，因无真实 key 留存，整个 anthropic section 一并删除

Added

  • 新增测试 TestConnectOpenClaw_PreservesExistingModels：确认用户已有 models 列表不被覆盖
  • 新增测试 TestDisconnectOpenClaw_RemovesKrouterAddedSectionWhenNoRealKey：无真实 apiKey 时整个节点被清除
  • 新增测试 TestDisconnectOpenClaw_PreservesRealApiKeyAndCustomModels：用户真实 apiKey 和自定义 models 在断开后完整保留

[2.0.28] - 2026-05-18

Added

  • Logs 页 SSE 实时追加：request_completed 事件直接推送到 Logs 页，新请求无需等待轮询即时出现
    • 单个稳定 SSE 连接；切换 agent 过滤器时通过 ref 避免 stale closure
    • 内存上限 2000 条；超出后自动丢弃尾部
  • Logs 页 Agent 下拉过滤器：选中 agent 后使用 ?agent=name 后端参数，只拉该 agent 的记录
    • 下拉选项从 /internal/agents 动态读取
    • 文本搜索框与 agent 过滤器可叠加使用
  • proxy → SSE 接线：proxy.Server.SetOnComplete 回调 + serve.go 接线，每次请求完成后立即广播 request_completed 事件（此前该事件类型存在但从未发送）
  • About 页显示 build_time：/internal/status 响应新增 build_time 字段；About 页在版本信息卡片中展示构建时间（unknown 时不显示）

Fixed

  • request_completed SSE 事件此前已在 Dashboard 监听但后端从未广播，现补全发送逻辑

[2.0.27] - 2026-05-18

Added

  • Agents 独立页（P0 gap 补全）
    • 左侧导航新增「Agents」入口（Bot 图标），位于 Dashboard 下方
    • 每个 agent 卡片显示：连接状态徽章、配置文件路径、provider 列表、今日请求数 / 今日费用 / 今日节省
    • Connect / Disconnect 按钮：直接修改 agent 配置文件（openclaw.json / settings.json / config.toml / shell rc），无需手动编辑
    • 连接后提示：Claude Code 需要打开新终端；OpenClaw / Cursor 需要重启
    • 展开 / 折叠 per-agent 请求日志（Show logs / Hide logs）
    • Re-detect 按钮强制重新扫描已安装 agent
  • POST /internal/agents/{name}/connect / POST /internal/agents/{name}/disconnect 端点
    • 支持 openclaw / cursor / hermes / claude-code
    • 找不到 agent 返回 404；不支持的 agent 名返回 400
  • GET /internal/logs?agent={name} 过滤参数，返回指定 agent 的最近请求记录
  • GET /internal/agents 返回值新增 stats 字段（requests_today / cost_today_usd / savings_today_usd）
  • storage.ListRequestsByAgent(ctx, agent, limit) — 带 agent WHERE 过滤的存储层方法
  • AgentInfo 字段加 JSON tag（name / config_path / cli_path），修复之前 PascalCase 序列化 bug

Changed

  • Providers 页移除「AI Agents」子区块（内容已移至独立 Agents 页）

[2.0.26] - 2026-05-18

Fixed

  • OpenClaw config 写入逻辑双重 bug 修复
    • Bug A（crash loop）：旧版 ConnectOpenClaw 向 models.providers.anthropic.apiKey 写入字面量 "${ANTHROPIC_API_KEY}"。OpenClaw 作为 LaunchAgent 运行，不继承 shell 环境，该占位符从不展开，直接作为无效 API key 发给 Anthropic，导致 OpenClaw crash loop。新版完全不写 apiKey——用户自己的真实 key 必须保留在 OpenClaw 配置里。
    • Bug B（字段覆盖）：旧版用 setNestedJSON 把整个 anthropic 节点替换成三个固定字段， 销毁用户原有的所有配置（如 minimax apiKey、models 列表）。新版改为 merge：只写 baseUrl 和 api，所有其他字段原样保留。
    • 旧版清理：DisconnectOpenClaw 现在会识别并删除旧版写入的 ${ANTHROPIC_API_KEY} 占位符，修复升级路径；真实 apiKey 永远不会被 Disconnect 删除。
    • 5 个测试覆盖：baseUrl+api 设置、apiKey 不注入、backup 创建、disconnect 保留真实 key、 disconnect 清除占位符

[2.0.25] - 2026-05-18

Added

  • GET /internal/agents — 新 API 端点，实时探测已安装的 AI agent 并报告 krouter 连接状态：
    • OpenClaw: 检查 ~/.openclaw/openclaw.json 是否存在，models.providers.anthropic.baseUrl 是否指向 http://127.0.0.1:8402，并列出配置文件中的所有 LLM provider 名称 （如 anthropic、minimax）
    • Claude Code: 检查 ~/.zshrc / ~/.bashrc / ~/.bash_profile 是否包含 krouter shell integration marker block
    • Cursor / Hermes: 检测文件是否存在（连接状态检测后续实现）
  • Providers 页 "AI Agents" 区块 — 展示每个 agent 的探测结果、连接状态 （Connected / Not connected 徽章）、配置文件路径、以及 agent 内部配置的 LLM provider 列表；每 15 s 自动刷新
  • IsOpenClawConnected(configPath) — 读取 OpenClaw 配置，判断是否已接入 krouter
  • ReadOpenClawProviderNames(configPath) — 读取 OpenClaw 配置内所有 provider 名称
  • IsClaudeCodeConnected(shellRCPath) — 检查 shell RC 是否包含 krouter marker
  • DetectAgentStatuses() — 在 DetectInstalledAgents() 基础上补充连接状态和 provider 列表
  • 8 个单元测试覆盖上述新函数

[2.0.24] - 2026-05-18

Changed

  • Dashboard UI 白色主题 — 参照 kinthai.ai 设计风格重新配色： 背景色从 #f7f8fa 改为 #f0f2f5，字体改为系统 UI 栈（-apple-system, BlinkMacSystemFont, ...）， 强制 light 模式（移除全部 dark: Tailwind 类），logo 更新为 kinthai.ai 完整渐变 SVG。
  • Tab 标题 — 浏览器标签从 "frontend" 改为 "KRouter"；favicon 路径修正为 /krouter/favicon.svg
  • 版本号 double-v 修复 — 侧边栏版本显示从 v{version} 改为 {version}，避免 git tag v2.0.x 导致显示 vv2.0.x

[2.0.23] - 2026-05-18

Fixed

  • 安装完成后 installer 进程自动退出 — krouter-installer 此前以 select {} 永久阻塞，安装向导结束后进程一直存在，导致用户在 Activity Monitor 里看到两个 "krouter" 进程（一个有图标的 installer、一个无图标的 daemon）。 现在 handleDaemonReady 在返回 ready: true 后 500 ms 关闭一个 shutdown channel，main.go 阻塞在该 channel 而非 select {}，收到信号后正常退出。 安装完成后用户只会看到一个 krouter daemon 进程。

[2.0.22] - 2026-05-18

Fixed

  • "KRouter took too long to start" — 根本原因 — 管理 API（port 8403） 从未注册 /health 路由；installer 的 daemon-ready 轮询一直得到 404 而非 200，永远返回 {ready: false}，导致 60 s 超时。现在 /health 已 注册且无需认证，1 个测试验证其行为。之前对 waitPortFree、bootout、 stopRunningDaemon 的修复解决的是"两个进程"和"拖拽安装"问题， 但超时 bug 的真正原因一直是这个缺失的端点。

[2.0.21] - 2026-05-18

Fixed

  • macOS: "krouter is still running" / 两个 krouter 进程 / 无法升级 — krouter-installer 现在启动时的第一个动作就是调用 launchctl bootout， 将正在运行的旧 daemon 从 launchd 监管中完全移除。此前：旧 daemon 注册了 KeepAlive=true，用户手动杀进程后 launchd 立即重启，导致永远无法替换； macOS Finder 看到同名进程报错 "krouter is still running"，用户无从下手。 现在用户只需打开新版安装包，installer 会自动停掉旧进程再走安装流程， 无需任何手动操作。Linux/Windows 同理（systemctl stop / schtasks /End）。

[2.0.20] - 2026-05-18

Fixed

  • macOS/Linux/Windows: "KRouter took too long to start" / two krouter processes — the proxy port-conflict guard in serve.go previously exited immediately (return nil) when port 8402 was already in use. During reinstall the old binary is still shutting down when launchd/systemd starts the new one, so the new binary would exit, launchd would wait its default 10 s ThrottleInterval before retrying, and the installer's 60 s poll window would time out. The guard now polls every 100 ms (up to 10 s) for the port to be freed; the new binary picks it up as soon as the old one releases it with no ThrottleInterval delay. Falls back to silent exit only if the port is still busy after 10 s (a permanent instance is genuinely running).
  • 4 unit tests covering waitPortFree: immediate return when free, waits until released, times out correctly, distinguishes bound vs free address

[2.0.19] - 2026-05-18

Added

  • krouter start / krouter stop CLI commands: proper daemon lifecycle management
    • macOS: launchctl bootstrap gui/<uid> <plist> / launchctl bootout gui/<uid> <plist>
    • Linux: systemctl --user start krouter / systemctl --user stop krouter
    • Windows: schtasks /Run /TN krouter-daemon / schtasks /End /TN krouter-daemon

Changed

  • macOS: LoadLaunchAgent now uses launchctl bootstrap/bootout instead of the deprecated load/unload + pgrep polling approach. launchctl bootout is synchronous and waits for the process to fully exit before returning, eliminating the port-conflict race without any process-name polling.

Removed

  • processExists (pgrep-based process checker) — no longer needed now that launchctl bootout provides synchronous process exit semantics

[2.0.18] - 2026-05-18

Fixed

  • macOS: two krouter processes / "KRouter took too long to start" — launchctl unload sends SIGTERM asynchronously and returns before the process exits; the immediately-following load would start the new binary while the old one still held the ports, causing the new binary to silently exit (port-conflict guard in serve.go). launchd then waited its default 10 s before retrying, exceeding the installer's 60 s poll window. LoadLaunchAgent now calls WaitForProcessExit after unload, polling pgrep -x krouter every 100 ms (up to 5 s) before issuing load, so the new binary always starts against free ports.

Added

  • config.WaitForProcessExit(name, timeout, interval, checkFn) — injectable process-exit poller extracted from LoadLaunchAgent for unit testing
  • 6 unit tests for WaitForProcessExit: immediate return when already gone, polls until checker returns false, times out correctly, passes correct name to checker, zero-timeout returns immediately, exits on first false response

[2.0.17] - 2026-05-18

Added

  • Installer tests — DoneStep (13 cases): covers initial render, spinner on click, navigation on first poll, navigation after later poll, timeout error (correct /krouter/ fallback URL), network-failure timeout, retry after timeout, error cleared on retry, finalize-410 swallowed, finalize-500 swallowed, missing redirect_url triggers fallback error
  • Installer tests — ShellStep (13 cases): covers initial render, Skip without API call, Applying… spinner, success banner + Open Dashboard button, API error message + retry, finalize called before first poll, navigation to redirect_url, timeout error with /krouter/ URL, connection-refused timeout, button reappears for retry, finalize-410 swallowed during Open Dashboard flow

Changed

  • DoneStep and ShellStep accept maxAttempts and pollIntervalMs props (default 40 / 1500 ms) to enable deterministic testing without fake timers

[2.0.16] - 2026-05-18

Changed

  • Dashboard URL: management UI now served at /krouter/ instead of /ui/ — bookmarks and shell output now show http://127.0.0.1:8403/krouter/
  • Dashboard branding: sidebar, active-nav highlight, preset buttons, quota bars, and action buttons now use the KRouter green brand palette (#25d366) to match the installer wizard; sidebar shows the KRouter logo and version tag
  • Routing Preset buttons: clicking a preset now gives immediate visual feedback (optimistic update) instead of waiting for the server round-trip to confirm

Fixed

  • Providers page: raw fetch now throws on non-2xx responses and surfaces an error message instead of silently rendering an empty list
  • Providers page: MiniMax added to the known-providers list so its setup hint (Set MINIMAX_API_KEY to enable) appears when the key is not configured

[2.0.15] - 2026-05-18

Fixed

  • macOS: "Open KRouter Dashboard" showed connection error on first install — two root causes fixed:
    1. launchctl load -w is a no-op when the service is already loaded (reinstall case), leaving the old process running; LoadLaunchAgent now unloads first so the daemon is always restarted with the updated binary.
    2. Even with the unload fix, timing cannot be fully guaranteed; the installer now shows a "Starting KRouter daemon…" spinner and polls /api/install/daemon-ready every 1.5 s (up to 60 s) before navigating to the dashboard, so the browser only opens the URL once the daemon is actually accepting connections.
  • macOS: skipping shell integration left MarkInstalled uncalled — DoneStep now calls finalize (idempotent) before polling, ensuring the ~/.kinthai/installed marker is always written regardless of which path through the wizard the user takes.

[2.0.14] - 2026-05-17

Fixed

  • macOS: install wizard opened a second browser tab at port 8405 — krouter-installer passed no SrcBinary to the orchestrator, so CopyBinary() fell back to os.Executable() (the installer itself) and copied it to ~/.local/bin/krouter; the LaunchAgent then started krouter-installer instead of krouter, which spawned a fresh wizard on port 8405 and opened a new browser tab showing the installer's first page. Fixed by detecting the co-located krouter daemon binary (e.g. inside the .app bundle's Contents/MacOS/) and using it as SrcBinary.
  • macOS: "Open KRouter Dashboard" button navigated before daemon was ready — handleFinalize now polls :8403/health for up to 10 s before minting the session ticket, ensuring the redirect URL carries a valid ticket instead of falling back to an unauthenticated /ui/ URL; the button shows "Opening dashboard…" while waiting.

[2.0.13] - 2026-05-15

Fixed

  • Linux: shell integration written to wrong file — DetectShellRC() mapped bash to ~/.bash_profile on all platforms; bash on Linux now correctly targets ~/.bashrc (macOS keeps ~/.bash_profile, which is correct for macOS login shells)
  • Daemon token clobbering on port conflict — when install --yes triggered multiple rapid daemon starts (e.g. idempotent re-runs), each short-lived instance would overwrite ~/.kinthai/internal-token before failing to bind, leaving the real daemon holding a stale token; serve now exits silently before writing the token if the proxy port is already bound

[2.0.12] - 2026-05-15

Fixed

  • SQLite driver replaced with pure-Go implementation — switched from mattn/go-sqlite3 (requires CGO) to modernc.org/sqlite (pure Go), enabling CGO_ENABLED=0 cross-compilation; removes the CGO toolchain requirement from all build environments including Windows cross-compilation

[2.0.11] - 2026-05-15

Fixed

  • MiniMax base URL corrected — domestic (Chinese mainland) API keys only work on api.minimax.chat; the adapter was incorrectly using api.minimax.io

[2.0.10] - 2026-05-15

Fixed

  • Windows: daemon not starting after installation — three root causes resolved:
    1. service_other.go build tag (!linux && !darwin) inadvertently caught Windows, making RegisterService() a silent no-op; replaced with a proper service_windows.go that calls RegisterTask + StartTask
    2. NSIS script registered the Task Scheduler task but never ran it, so the daemon only started on the next login; added schtasks /Run /TN "krouter-daemon" immediately after task-install
    3. orchestrator.RegisterService() hardcoded ~/.local/bin/krouter (a Linux path); replaced with platformDaemonPath() which returns %LOCALAPPDATA%\kinthai\krouter.exe on Windows

Added

  • config.StartTask() — runs the Task Scheduler task immediately via schtasks /Run (Windows only; stub on other platforms)
  • config.TaskName() — exports the task name constant ("krouter-daemon")

[2.0.9] - 2026-05-15

Fixed

  • Transparent proxy correctness: removed accidental API key injection from the Anthropic-protocol adapter. krouter now forwards the client's x-api-key header unchanged to all Anthropic-compatible upstreams (including MiniMax). Previously, MiniMax requests incorrectly attempted to inject a server-side MINIMAX_API_KEY.

Added

  • Test coverage for ticket and session expiry (TestExchangeTicket_ExpiredFails, TestSessionCookie_ExpiredFails)
  • TestOrchestrator_ShellIntegration_Fish — verifies Fish shell config.fish path is created with the krouter marker block
  • TestListen_PortConflict_TriesNext — verifies install server binds the next port when the requested port is already occupied
  • TestWriteLaunchAgentPlist_ReturnsError_OnNonMacOS — verifies the macOS LaunchAgent stub returns an error on Linux/Windows

[2.0.8] - 2026-05-14

Added

  • MiniMax provider adapter (internal/providers/minimax): Anthropic-messages protocol at https://api.minimax.io/anthropic, enabled via MINIMAX_API_KEY
  • Routing engine now prefers the provider that explicitly lists the requested model (pickProviderForModel), preventing MiniMax-model requests from being mis-routed to the Anthropic upstream

[2.0.7] - 2026-05-13

Fixed

  • PATCH /internal/settings returned 503 because apiSrv.SetSettings() was never called in serve.go

[2.0.6] - 2026-05-13

Fixed

  • SPA routes (e.g. /ui/logs) returned HTTP 301 due to http.FileServer's /index.html → ./ canonicalization; fixed by reading index.html directly
  • Linux systemd user service: krouter install --yes now runs loginctl enable-linger and sets XDG_RUNTIME_DIR=/run/user/<uid> before calling systemctl --user, so installation works on SSH-only servers without an active login session

[2.0.0] - 2026-05-13

BREAKING: Replaced Wails v2 desktop GUI with embedded React web UI served by the daemon. This changes the install flow, binary distribution, and GUI entry point.

Changed

  • GUI architecture: daemon now embeds React web UI at http://127.0.0.1:8403/ui/ instead of shipping a separate Wails desktop binary
  • Install flow: replaced Wails app with krouter-installer, a standalone binary that serves a browser-based wizard at :8404 (no Electron, no native window)
  • Two-binary distribution: krouter (daemon + CLI) + krouter-installer (one-shot wizard, exits after setup completes)
  • Authentication: management API now supports session cookies in addition to Bearer tokens; ticket-exchange flow allows tray/CLI to open the web UI without re-entering credentials

Added

  • krouter install — TTY installer with --yes / --dry-run / --skip-agents flags
  • krouter uninstall — uninstaller with --keep-data flag
  • Web UI pages: Dashboard, Logs, Providers, Settings, Announcements, About
  • SSE event stream at GET /internal/events for real-time UI updates
  • Desktop notifications via gen2brain/beeep (CGO-free; quota warnings, announcements, upgrade available)
  • Session cookie auth (POST /internal/auth/ticket → GET /internal/auth/exchange)
  • GET /internal/settings and PATCH /internal/settings endpoints
  • GET /internal/budget endpoint (today's savings breakdown)
  • macOS .dmg release artifact (krouter.app bundle, LSUIElement=true)
  • Linux .AppImage release artifact
  • Windows krouter-setup.exe NSIS installer (launches wizard on completion)
  • Signed manifest.json + manifest.json.sig on every release

Removed

  • cmd/krouter-gui/ — Wails v2 desktop application and all Wails dependencies

[1.0.3] - 2026-05-13

Patch release; CI pipeline fixes only. No functional changes from v1.0.0.

[1.0.0] - 2026-05-13

Initial release (Wails-based architecture; superseded by v2.0.0).

Added

  • HTTP proxy on 127.0.0.1:8402 (Anthropic + OpenAI protocols)
  • Routing engine with Balanced + Saver presets
  • Providers: Anthropic, OpenAI, DeepSeek, Groq, Moonshot, GLM, Qwen
  • LaunchAgent / systemd --user / Windows Task Scheduler integration
  • SQLite-based per-request logging
  • Notification center with 6h CDN poll
  • Self-update with ECDSA manifest verification
  • LAN remote access with HTTPS and pairing tokens
  • CLI: status, logs, budget, config, test