[Bug]: GENERATION_FAILED (fp: 3bb50f8c)

[Tilmirs]

Description

使用deepseek 报错

Steps to reproduce

1 Access to the third-party APIKEY
2 Calling deepseek directly reports an error after use, other models can1 Access to the third-party APIKEY
2 Calling deepseek directly reports an error after use, other models can

Expected behavior

正常可以使用

Actual behavior

Error invoking remote method 'codesign:v1:generate': CodesignError: 400 Failed to deserialize the JSON body into the target type: messages[0].role: unknown variant developer, expected one of system, user, assistant, tool, latest_reminder at line 1 column 51783 — user notes: 接入三方deespseek的api报错

open-codesign version

0.1.4

Platform

Windows

OS version

Windows 11 (10.0.26200)

Model provider (if relevant)

None

Error code

GENERATION_FAILED

Diagnostics bundle

Bundle saved locally at ~\Downloads\open-codesign-diagnostics-2026-05-08T10-56-22.zip. Attach it to this issue after submitting.

Logs

[2026-05-08 18:55:43.568] [info]   (main:ipc) [generate] step=send_request {
  runId: 'mowsu8cu-sp7u7r',
  generationId: 'mowsu8cu-sp7u7r',
  provider: 'custom-my-rm9m',
  modelId: 'deepseek-v4-pro'
}
[2026-05-08 18:55:43.569] [info]   (main:ipc) agent.turn_start { runId: 'mowsu8cu-sp7u7r', generationId: 'mowsu8cu-sp7u7r' }
[2026-05-08 18:55:43.570] [info]   (main:ipc) [context-prune] step=caps {
  runId: 'mowsu8cu-sp7u7r',
  generationId: 'mowsu8cu-sp7u7r',
  messages: 6,
  before: 1681,
  after: 1681,
  textLimit: 8192,
  toolInputLimit: 24576,
  toolResultLimit: 8192,
  window: 3
}
[2026-05-08 18:55:44.438] [info]   (main:ipc) agent.turn_end {
  runId: 'mowsu8cu-sp7u7r',
  generationId: 'mowsu8cu-sp7u7r',
  deltas: 0,
  tools: 0
}
[2026-05-08 18:55:44.441] [info]   (main:ipc) agent.end { runId: 'mowsu8cu-sp7u7r', generationId: 'mowsu8cu-sp7u7r' }
[2026-05-08 18:55:44.442] [error]  (main:ipc) [generate] step=send_request.fail {
  runId: 'mowsu8cu-sp7u7r',
  generationId: 'mowsu8cu-sp7u7r',
  provider: 'custom-my-rm9m',
  modelId: 'deepseek-v4-pro',
  ms: 873,
  stopReason: 'error'
}
[2026-05-08 18:55:44.443] [error]  (main:ipc) generate.fail {
  runId: 'mowsu8cu-sp7u7r',
  generationId: 'mowsu8cu-sp7u7r',
  ms: 879,
  provider: 'custom-my-rm9m',
  modelId: 'deepseek-v4-pro',
  baseUrl: '[url omitted]',
  status: 400,
  message: '400 Failed to deserialize the JSON body into the target type: messages[0].role: unknown variant `developer`, expected one of `system`, `user`, `assistant`, `tool`, `latest_reminder` at line 1 column 51783',
  code: 'PROVIDER_ERROR'
}
[2026-05-08 18:55:44.451] [error]  (renderer:console) [store] applyGenerateError {"generationId":"mowsu8cu-sp7u7r","designId":"d3717869-6632-4490-86ff-eabd70e37bb1","message":"Error invoking remote method 'codesign:v1:generate': CodesignError: 400 Failed to deserialize the JSON body into the target type: messages[0].role: unknown variant `developer`, expected one of `system`, `user`, `assistant`, `tool`, `latest_reminder` at line 1 column 51783"} {}
[2026-05-08 18:55:44.453] [info]   (chat-messages-ipc) chat.append {
  designId: 'd3717869-6632-4490-86ff-eabd70e37bb1',
  seq: 8,
  kind: 'error'
}

[github-actions]

感谢您的反馈！

您遇到的错误 unknown variant 'developer' 说明第三方 DeepSeek API 不识别 developer 角色。在 Open CoDesign 中，当检测到模型为推理模型（如 deepseek-reasoner 或 deepseek-v4-pro 系列）时，会使用 developer 角色（参照 OpenAI 的 reasoning 模型格式），但您所使用的第三方 API 端点不支持该角色，只接受 system、user、assistant、tool 等传统角色。

相关代码路径：

• .github/scripts/deepseek-common.mjs:226 — 将 deepseek-v4-pro 识别为推理模型并启用 developer 角色
• packages/core/src/agent.ts / packages/providers — 构建消息时根据推理模式设置角色

可能的解决方法：

1. 如果您的 deepseek-v4-pro 实际上是普通对话模型而非推理模型，请检查自定义提供者的配置中是否有“启用推理”选项（如果有，请关闭）；或者尝试使用官方 DeepSeek API 端点。
2. 如果您的第三方 API 兼容 OpenAI，可以尝试将模型 ID 改为官方名称（如 deepseek-chat），避免触发推理模型分支。
3. 如果必须使用该第三方 API，可能需要联系其提供商确认是否支持 developer 角色，或等待 Open CoDesign 后续版本增加角色映射配置。

为了进一步分析，请提供以下信息（最少必要）：

• 您使用的第三方 API 提供商/代理 URL（可脱敏处理）
• deepseek-v4-pro 模型在该 API 上是否是推理模型？通常 DeepSeek 的推理模型是 deepseek-reasoner，v4-pro 可能只是对话模型
• 在自定义提供者配置中，是否有“模型类型”或“推理模式”的开关？

感谢您花时间报告问题，我们会继续改进兼容性！

---

Open-CoDesign Bot

[rsxdalv]

Afaik it's resolved, the new version just isn't released yet. I hope it gets released soon, because v0.1.4 lacks this fix.