chore(release): bump to v0.7.10 — 配置写回保护(导入基线 + 未知供应商类型原样保留)
Release / Version consistency (push) Canceled after 0s
Release / Attach macOS install script (push) Canceled after 0s
Release / Build (macos-latest) (push) Canceled after 0s
Release / Build (ubuntu-latest) (push) Canceled after 0s
Release / Build (windows-latest) (push) Canceled after 0s
Release / Version consistency (push) Canceled after 0s
Release / Attach macOS install script (push) Canceled after 0s
Release / Build (macos-latest) (push) Canceled after 0s
Release / Build (ubuntu-latest) (push) Canceled after 0s
Release / Build (windows-latest) (push) Canceled after 0s
This commit is contained in:
1 parent
67db19eda4
commit
7435198fcc
6 files changed
+18
-4
No files matched your search
@@ -543,6 +543,12 @@ A: 需要分两步:
|
||||
**Q: 切换会覆盖其他供应商吗?**
|
||||
A: 不会。Kimi Code 的 `config.toml` 始终写入全部供应商,仅 `default_model` 决定生效项。这与 CLI 原生 `/provider` 行为一致。
|
||||
|
||||
**Q: 在 Kimi Code CLI 里新增的顶层配置节(如 `[task]`/`[swarm]`)会被保存时删掉吗?**
|
||||
A: 不会(v0.7.10 起)。保存时以加载配置那一刻的顶层键为基线,CLI 后加的节原样保留;只有在本应用中显式删除的节才会从 `config.toml` 移除。
|
||||
|
||||
**Q: 遇到 Kimi Code 新增的供应商类型(`type` 值)会怎样?**
|
||||
A: 原样保留,不再改写为 `kimi`。编辑界面会显示原始类型值(标注"未知类型");该供应商不支持的操作(如模型发现)会返回明确错误提示。
|
||||
|
||||
**Q: 新增/激活的供应商位置怎么变?**
|
||||
A: 自动提升到列表最前,UI 立即反映。
|
||||
|
||||
|
||||
Reference in new issue
Block a user