feat: rename DeepSeek TUI agent to CodeWhale

[chenmofei]

Background

deepseek-tui 已正式更名为 CodeWhale（v0.8.41, 2026-05-23）。旧版 deepseek 和 deepseek-tui 二进制将作为废弃兼容 shim 保留一个发布周期，v0.9.0 移除。

为什么要改

1. 安装 CodeWhale 的用户检测不到：当前 main 分支 agent id 为 deepseek、bin 为 deepseek，已安装 CodeWhale 的用户无法被识别
2. deepseek 命名空间冲突：agent id deepseek 与未来 DeepSeek 官方的 Code Agent 可能产生冲突，本次完整释放，预留给官方
3. GUI 名称过时：显示的是旧名，未反映更名后的 CodeWhale

Changes

两条独立 AgentDef，互相 fallbackBins 检测

安装任一二进制，GUI 两个卡片均显示为可用：

Property	codewhale	deepseek-tui
id	codewhale	deepseek-tui
label	CodeWhale	DeepSeek TUI
bin	codewhale	deepseek-tui
fallbackBins	deepseek-tui	codewhale
envOverride	CODEWHALE_BIN	DEEPSEEK_TUI_BIN
vendor	CodeWhale	DeepSeek
protocol	argv	argv
fallbackModels	相同	相同

调用逻辑

buildArgv / parseLineWithState / close-path 均新增 codewhale 分支，共享 exec --auto 调用。

命名空间释放

deepseek 不再作为 agent id、bin 或标识符出现，完整留给未来 DeepSeek 官方 Code Agent。

Behavior

GUI

安装的二进制	GUI 显示
codewhale	CodeWhale / DeepSeek TUI 均可用
deepseek-tui	CodeWhale / DeepSeek TUI 均可用
均未安装	两个卡片均显示未安装

CLI

命令	结果
-a codewhale	调用 codewhale
-a deepseek-tui	调用 deepseek-tui
-a deepseek	unknown agent（预留官方）

Files Changed

• next/src/lib/agents/detect.ts — 新增 codewhale / 改 deepseek-tui，互相 fallbackBins
• cli/src/agents-detect.ts — 同上
• next/src/lib/agents/argv.ts — buildArgv/parseLineWithState/错误提示 新增 codewhale
• next/src/lib/agents/invoke.ts — close-path 新增 codewhale
• cli/src/agents-invoke.ts — buildArgv/parseLineWithState/close-path/错误提示 新增 codewhale
• next/src/components/settings-modal.tsx — VENDOR_GRADIENT 新增 CodeWhale
• next/src/components/welcome-modal.tsx — VENDOR_HINT 新增 CodeWhale / DeepSeek
• cli/README.md — CodeWhale + DeepSeek TUI 两行
• cli/src/tests/agents-detect.test.ts — codewhale protocol 测试
• cli/src/tests/agents-invoke.test.ts — codewhale close-path 测试

Test Results

7 files / 133 tests passed / CLI typecheck OK / Next typecheck OK

[PerishCode]

@chenmofei thanks for the rename — splitting codewhale and deepseek-tui into two AgentDef entries with mutual fallbackBins is a clean way to ride out the v0.8.x deprecation cycle, and the GUI/CLI surfaces (vendor gradients, install hints, error-message agent lists, exec --auto argv) line up consistently across both packages. One non-blocking correctness finding on the Next-side close-path is noted inline; the equivalent fix already lives in the CLI sibling.

_{🔁 Powered by Looper · runner=reviewer · agent=claude-code · An autonomous AI dev team for your GitHub repos.}

[PerishCode]

Duplicate close-path delta for codewhale / deepseek-tui (and pre-existing aider).

The parse(stdoutBuf) loop above already emits the residual buffer as a delta for these three agents — the parser at next/src/lib/agents/argv.ts:235 returns [{ kind: "delta", text: trimmed + "\n" }] whenever the agent is aider | codewhale | deepseek-tui. This added safeEnqueue({ type: "delta", text: stdoutBuf }) then sends the same residual text a second time, so any final stdout chunk that doesn't end on a newline (the typical end-of-stream shape for deepseek-tui / codewhale running exec --auto) is delivered twice.

Why it matters: downstream consumers concatenate every delta into the rendered/saved HTML, so the duplicated tail — often a chunk of the actual document including a </html> closer — leaks into the preview and any persisted/exported file. Before this PR the buggy path covered one agent (deepseek); after the rename it covers three (aider, codewhale, deepseek-tui), so the regression footprint grows even though the bug itself pre-existed.

Evidence the fix is missing only on the Next side: the CLI sibling cli/src/agents-invoke.ts:595-604 uses if/else for exactly this case (commit 889878e — "fix(cli): deduplicate aider/deepseek output …"), and cli/src/__tests__/agents-invoke.test.ts:489-507 asserts expect(deltas).toHaveLength(1) for codewhale close-path with a no-trailing-newline payload. There is no equivalent test on the Next side, but the dispatch code is the only structural difference.

Suggested change: mirror the CLI structure so the raw enqueue replaces (rather than stacks onto) the parser dispatch for these three agents:

} else if (stdoutBuf) {
  if (opts.agent === "aider" || opts.agent === "codewhale" || opts.agent === "deepseek-tui") {
    safeEnqueue({ type: "delta", text: stdoutBuf });
  } else {
    for (const part of parse(stdoutBuf)) {
      if (part.kind === "delta") safeEnqueue({ type: "delta", text: part.text });
      else if (part.kind === "html") safeEnqueue({ type: "html", text: part.text });
      else if (part.kind === "meta") safeEnqueue({ type: "meta", key: part.key, value: part.value });
    }
  }
}

[chenmofei]

Fixed in 71204db — mirrored the CLI's if/else structure.

[chenmofei]

Good catch! Fixed in 71204db — mirrored the CLI's if/else structure so the raw enqueue replaces (rather than stacks onto) the parser dispatch for aider/codewhale/deepseek-tui. Typecheck & tests still green.

[PerishCode]

@chenmofei thanks for the quick turn-around on the close-path fix in 71204db — the if/else now mirrors the CLI sibling exactly, so the parser dispatch and the raw stdoutBuf enqueue are mutually exclusive for aider / codewhale / deepseek-tui and the duplicate-tail regression is gone. Spot-checked the rest of the rename surface (mutual fallbackBins in detect.ts, the new codewhale branches in buildArgv / parseLineWithState, the VENDOR_GRADIENT + VENDOR_HINT entries, and the updated agent list in UnsupportedAgentProtocolError) and everything lines up consistently. Nice clean follow-up.

_{🔁 Powered by Looper · runner=reviewer · agent=claude-code · An autonomous AI dev team for your GitHub repos.}

[lefarcen]

Quick status update: @PerishCode has approved the current head, and I don’t see any author action needed right now.

@Eli-tangerine, when you have a chance, could you take the product pass on the user-visible agent rename / CLI ID change? Once product review and checks are in, this can move toward merge.

[chenmofei]

最新情况：已经批准了现任负责人的人选，目前看来无需采取任何进一步行动。

@Eli-tangerine如果有机会的话，能否请你们处理一下用户可见的界面元素名称的更改，以及 CLI ID 的修改呢？一旦产品审查和测试工作完成，就可以进行合并了。

@Eli-tangerine 这个用户好像不存在了？我看账号页面提示 404

[lefarcen]

你说得对，我这边也确认这个 GitHub 用户页目前是 404。这个不是你需要处理的问题；我会把产品 review 改走内部通道，并让维护侧确认正确的公开 reviewer 配置。

当前代码侧 @PerishCode 已经 approve，后续主要还差产品确认和检查状态。谢谢提醒 🙏