[Bug]: DeepSeek Harness (dsh) fails with INVALID_REQUEST when "CLI default" (default) model is selected

Abierto
  • ¿Algo no está bien?
#461 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

@fx-kurumi ya está trabajando en esto.

Desde el 13/11/2026.

  • #482 de @fx-kurumi — abierto

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
25/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Estancado
Stack tecnológico
go
Área
ai, backend

Línea de trabajo

Start with the trace the issue gives: the placeholder model in internal/httpapi/assistant_models.go, the splitting in assistantModelEngine in internal/httpapi/assistant.go, and the AgentCLIDeepSeek branch of ApplyAgentCLICredential in internal/runtime/agent_cli.go. Pull request #482 is already open against this issue, so check its diff before starting. Done means a dsh request with the CLI default selected no longer sends model "default" to the DeepSeek API.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Component / host

Platform — web / API

Edition

Platform

LoopForge version

main at b751e09 (v0.3.6-29-gb751e09)

What happened?

When using DeepSeek Harness (dsh) in AI Chat and selecting the CLI default model option (model ID "default"), every message fails with "AI 助手生成失败，请稍后重试".

Switching the model selector to an explicit model such as DeepSeek V4.1 Flash (deepseek-flash) works immediately with the exact same API key.

Root cause in code:

  1. internal/httpapi/assistant_models.go returns a placeholder entry {ID: "default", Name: "CLI default"} for non-CodeBuddy executors (executor=dsh, etc.).
  2. internal/httpapi/assistant_engines.go (assistantRequestModel) prefixes it to "dsh:default", and internal/httpapi/assistant.go (assistantModelEngine) splits out engineModel = "default" without normalizing "default" to "" for non-CodeBuddy CLIs.
  3. internal/runtime/agent_cli.go (ApplyAgentCLICredential, case AgentCLIDeepSeek) only checks if model != "", so it writes {"id": "agent-default-model", "config": {"provider": "deepseek-official", "model": "default"}} into .dsh/agentflow-model.json via --patch, overriding dsh's own built-in default model.
  4. dsh sends "model": "default" to the DeepSeek API, which rejects it with 400 INVALID_REQUEST, and assistantGenerationFailure maps it to the generic "AI 助手生成失败，请稍后重试" error.

(Note: Other non-CodeBuddy CLIs such as Codex in assistant_engine_codex.go and other AgentCLI branches in agent_cli.go also pass model = "default" through instead of omitting it.)

Reproduction
  1. Configure a valid DeepSeek Harness API Key in personal settings (official endpoint, empty Base URL) and ensure dsh is installed.
  2. In AI Chat, switch the CLI selector to DeepSeek Harness and keep the model selector on CLI default (default).
  3. Send any message (e.g. hello？？).
  4. Observe the failure (AI 助手生成失败，请稍后重试), while switching to DeepSeek V4.1 Flash succeeds.
Screenshots
Scenario Screenshot
DeepSeek Harness + CLI default fails 01-dsh-cli-default-failed.png
Switching model to DeepSeek V4.1 Flash 02-dsh-flash-selected.png
DeepSeek V4.1 Flash replies normally 03-dsh-flash-succeeded.png
Sanitized diagnostics
assistant CLI session=<redacted>: DeepSeek Harness 运行结束：error; stderr=[llm-deepseek-api-key] model listing from https://api.deepseek.com/models loaded 2 model(s), skipped 0 row(s) | dsh: INVALID_REQUEST: The supported API model names are deepseek-flash, deepseek-v4-pro, but you passed default. (request_id: <redacted>)
Safety checks
  • I removed credentials, private endpoints, internal identifiers, and personal data.
  • I searched existing issues for duplicates.
中文说明
组件 / 宿主

Platform — web / API

版本形态

Platform

LoopForge 版本

main 提交 b751e09（v0.3.6-29-gb751e09）

现象描述

在 AI 对话中切换为 DeepSeek Harness（dsh） 并保持模型选择器为 CLI default（模型 ID 为 "default"）时，发送任意消息都会报错 "AI 助手生成失败，请稍后重试"。

使用同一把 API Key，只要把模型手动切换为 DeepSeek V4.1 Flash（deepseek-flash），即可立即正常回复。

代码根因定位：

  1. internal/httpapi/assistant_models.go 为非 CodeBuddy 执行器（如 executor=dsh）返回了占位模型 {ID: "default", Name: "CLI default"}。
  2. internal/httpapi/assistant_engines.go（assistantRequestModel）将其拼成 "dsh:default"，随后 internal/httpapi/assistant.go（assistantModelEngine）拆出 engineModel = "default"，但没有为非 CodeBuddy CLI 将 "default" 归一为空字符串 ""。
  3. internal/runtime/agent_cli.go（ApplyAgentCLICredential 的 AgentCLIDeepSeek 分支）只判断了 if model != ""，直接把 {"id": "agent-default-model", "config": {"provider": "deepseek-official", "model": "default"}} 写入 .dsh/agentflow-model.json 并通过 --patch 注入，覆盖了 dsh 本身的内置默认模型。
  4. dsh 把 "model": "default" 发给 DeepSeek 接口后触发 400 INVALID_REQUEST，最终被 assistantGenerationFailure 兜底成 "AI 助手生成失败，请稍后重试"。

（附注：同构的非 CodeBuddy CLI 链路，如 assistant_engine_codex.go 与 agent_cli.go 其他分支，同样存在未将 "default" 归一为空字符串的问题。）

复现步骤
  1. 在个人配置中填写有效的 DeepSeek Harness API Key（默认官方端点，Base URL 留空）并确保 dsh 已安装。
  2. 在 AI 对话底部将 CLI 切换为 DeepSeek Harness，模型保持 CLI default（default）。
  3. 发送任意消息（例如 hello？？）。
  4. 观察到报错 AI 助手生成失败，请稍后重试；将模型切换为 DeepSeek V4.1 Flash 后同一会话即可正常回复。
复现截图
场景 截图
DeepSeek Harness + CLI default 失败 01-dsh-cli-default-failed.png
切换为 DeepSeek V4.1 Flash 02-dsh-flash-selected.png
DeepSeek V4.1 Flash 正常回复 03-dsh-flash-succeeded.png
脱敏诊断日志
assistant CLI session=<redacted>: DeepSeek Harness 运行结束：error; stderr=[llm-deepseek-api-key] model listing from https://api.deepseek.com/models loaded 2 model(s), skipped 0 row(s) | dsh: INVALID_REQUEST: The supported API model names are deepseek-flash, deepseek-v4-pro, but you passed default. (request_id: <redacted>)
安全检查
  • 已移除所有凭据、私有端点、内部标识符与个人数据。
  • 已检索现有 Issue 确认无重复提交。
Lenguaje dominante
Go
Estrellas
141
Forks
28
Merge medio
1 d 15 h
PR fusionados (30 d)
113

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de Tencent/LoopForge

Todos los issues de Tencent/LoopForge

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.