Bug description
Since this morning, requests in responses API mode are rejected by the provider with a 400 error. Switching the same provider/model to chat (chat completions) mode works fine.
This is a regression: responses mode worked normally until yesterday with the same setup. The provider's error suggests ZCode's responses-mode request is now missing the required input.type parameter.
Steps to reproduce
- Set the provider API to
responses mode.
- Send any message with DeepSeek V4 Flash.
- The turn fails with a 400
MissingParameter error (see below).
Switching the provider API to chat mode with the same model makes it work again.
Error details
- provider:
new-provider
- model:
deepseek/deepseek-v4-flash
- reason:
invalid_request (status 400, not retryable)
- TraceID:
0af922c4-84b4-45ae-9062-6a7d2730a8b1
- Provider response:
{"type":"BadRequest","code":"MissingParameter","message":"The request failed because it is missing `input.type` parameter. Request id: 02179055413037678af8113c224ccdd69578c3b63d1e71a579929 trace_id: 706c96776d86abe6b54c9ced0e850c37"}Expected behavior
Responses-mode requests should include the input.type parameter and be accepted, as they were before today.
中文说明（Chinese summary）
问题描述：
从今天早上开始，使用 responses API 模式发请求会被服务商以 400 错误拒绝；把同样的模型换成 chat（chat completions）模式就一切正常。
在此之前（昨天为止）同样的配置一直正常，属于突然出现的回归问题。服务商的报错提示表明：ZCode 在 responses 模式下发出的请求缺少了必需的 input.type 参数。
复现步骤：
- 把 provider 的 API 设置为
responses 模式；
- 用 DeepSeek V4 Flash 随便发一条消息；
- 回合失败，报 400
MissingParameter 错误（详情见上方英文部分）。
把 provider 的 API 换成 chat 模式后，同一个模型即可正常使用。
报错详情：
- provider：
new-provider
- model：
deepseek/deepseek-v4-flash
- reason：
invalid_request（状态码 400，不可重试）
- TraceID：
0af922c4-84b4-45ae-9062-6a7d2730a8b1
- 服务商返回：
{"type":"BadRequest","code":"MissingParameter","message":"The request failed because it is missing `input.type` parameter. Request id: 02179055413037678af8113c224ccdd69578c3b63d1e71a579929 trace_id: 706c96776d86abe6b54c9ced0e850c37"}期望行为：
responses 模式的请求应像今天之前一样，带上 input.type 参数并被正常接受。
Bug description
Since this morning, requests in responses API mode are rejected by the provider with a 400 error. Switching the same provider/model to chat (chat completions) mode works fine.
This is a regression: responses mode worked normally until yesterday with the same setup. The provider's error suggests ZCode's responses-mode request is now missing the required
input.typeparameter.Steps to reproduce
responsesmode.MissingParametererror (see below).Switching the provider API to
chatmode with the same model makes it work again.Error details
new-providerdeepseek/deepseek-v4-flashinvalid_request(status 400, not retryable)0af922c4-84b4-45ae-9062-6a7d2730a8b1{"type":"BadRequest","code":"MissingParameter","message":"The request failed because it is missing `input.type` parameter. Request id: 02179055413037678af8113c224ccdd69578c3b63d1e71a579929 trace_id: 706c96776d86abe6b54c9ced0e850c37"}Expected behavior
Responses-mode requests should include the
input.typeparameter and be accepted, as they were before today.中文说明（Chinese summary）
问题描述：
从今天早上开始，使用 responses API 模式发请求会被服务商以 400 错误拒绝；把同样的模型换成 chat（chat completions）模式就一切正常。
在此之前（昨天为止）同样的配置一直正常，属于突然出现的回归问题。服务商的报错提示表明：ZCode 在 responses 模式下发出的请求缺少了必需的
input.type参数。复现步骤：
responses模式；MissingParameter错误（详情见上方英文部分）。把 provider 的 API 换成
chat模式后，同一个模型即可正常使用。报错详情：
new-providerdeepseek/deepseek-v4-flashinvalid_request（状态码 400，不可重试）0af922c4-84b4-45ae-9062-6a7d2730a8b1{"type":"BadRequest","code":"MissingParameter","message":"The request failed because it is missing `input.type` parameter. Request id: 02179055413037678af8113c224ccdd69578c3b63d1e71a579929 trace_id: 706c96776d86abe6b54c9ced0e850c37"}期望行为：
responses 模式的请求应像今天之前一样，带上
input.type参数并被正常接受。