new-api 强行把我的gpt-5.2的请求,里面的role:system 转换成了 role:developer,导致报错.

[JsonSong89]

例行检查

• 我已确认目前没有类似 issue
• 我已确认我已升级到最新版本
• 我已完整查看过项目 README，尤其是常见问题部分
• 我理解并愿意跟进此 issue，协助测试和提供反馈
• 我理解并认可上述内容，并理解项目维护者精力有限，不遵循规则的 issue 可能会被无视或直接关闭

问题描述
请求某中转渠道,模型是 openai/gpt-5.2
我传递给new-api的请求体是:

{
    "model": "openai/gpt-5.2",
    "messages": [
        {
            "role": "system",
            "content": "你现在是一名资深的软件工程师，在这个角色下,使用中文为我解答以下问题。"
        },
        {
            "role": "user",
            "content": "直接查询知识库,当前最新vue的版本是多少?只需要输出版本号即可."
        }
    ],
    "stream": true,
    "stream_options": {
        "include_usage": true
    }
}

我劫持响应之后,发现new-api发给llm上游的请求变成了:

{
    "messages": [
      {
        "content": "你现在是一名资深的软件工程师，在这个角色下,使用中文为我解答以下问题。",
        "role": "developer"
      },
      {
        "content": "直接查询知识库,当前最新vue的版本是多少?只需要输出版本号即可.",
        "role": "user"
      }
    ],
    "model": "openai/gpt-5.2",
    "stream": true,
    "stream_options": {
      "include_usage": true
    }
  }

复现步骤
v0.10.4
配置一个openai渠道,没有任何其他覆写配置.

开启透传模式,即可恢复正常,不过我还是需要模型重定向功能的.

预期结果
不要修改我的请求体,或者提供开关,关闭请求体修改功能.

我知道openai官方,gpt5系列都换成了 developer,但是还是有很多服务商,是使用的老v1/chat/completions规范
所以希望能提供开关,控制这种请求体修改

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

✅ Successfully generated implementation plan.

💡 Use @coderabbitai <feedback> to replan

Examples

• Example 1
• Example 2

---

🔗 Related PRs

#1441 - feat: 支持渠道级透传选项，支持设置渠道系统提示词 [merged]
#1761 - feat: 改进Claude响应转OpenAI响应 [merged]
#1811 - 重构ollama渠道 [merged]
#1897 - feat: 添加 openrouter-enterprise 支持 [merged]
#1950 - fix: missing field & field control [merged]

👤 Suggested Assignees

• creamlike1024
• Calcium-Ion
• somnifex
• seefs001

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[coderabbitai]

Coding Plan

Approach

Add a channel-level toggle to control the automatic role transformation from "system" to "developer" for GPT-5 and O-series models, allowing users to disable this transformation when working with upstream providers that use the older v1/chat/completions specification.

Observations

This is a Go-based API relay/proxy system that forwards requests to various LLM providers. The system uses a channel adapter pattern where each provider has an adaptor that transforms requests. Channel-specific behavior is controlled through settings stored in ChannelSettings (for general toggles) and ChannelOtherSettings (for API-specific configurations). The OpenAI adaptor in relay/channel/openai/adaptor.go currently performs unconditional role transformations for GPT-5 and O-series models, converting the first message's role from "system" to "developer" to align with OpenAI's latest API specification.

Assumptions

Assumption 1: Setting Default Behavior

Options Considered:

• Enable transformation by default (current behavior continues unless explicitly disabled)
• Disable transformation by default (users must opt-in to the new developer role behavior)

Chosen Option: Enable transformation by default (current behavior continues unless explicitly disabled)

Rationale: This maintains backward compatibility with existing channel configurations and aligns with OpenAI's official specification. Users who need the legacy behavior can explicitly disable it per channel. This follows the principle of least surprise—existing users won't see behavior changes, while new users wanting legacy behavior can easily configure it.

💡 User Tips

Regenerate the plan with different choices with @coderabbitai <feedback>.

Implementation Steps

Phase 1: Add Configuration Toggle

Define the new channel-level setting that will control role transformation behavior.

Add DisableDeveloperRoleTransform Field to ChannelSettings

Add a new boolean flag to the ChannelSettings structure that controls whether the system→developer role transformation should be skipped.

• Add DisableDeveloperRoleTransform bool field to the ChannelSettings struct in dto/channel_settings.go with JSON tag disable_developer_role_transform
• Follow the existing pattern of other boolean flags in the struct (e.g., ForceFormat, ThinkingToContent)
• Add a descriptive comment explaining the field controls role transformation for GPT-5 and O-series models
• The reflection-based configuration system will automatically handle persistence and loading without additional code changes

🤖 Prompt for AI agents

Add a new channel-level configuration toggle to control role transformation
behavior.

In `dto/channel_settings.go`:
- Add `DisableDeveloperRoleTransform bool` field to `ChannelSettings` struct
with JSON tag `disable_developer_role_transform`
- Follow existing boolean flag patterns (e.g., `ForceFormat`,
`ThinkingToContent`)
- Add comment explaining this controls system→developer role transformation for
GPT-5 and O-series models

Phase 2: Apply Setting in Request Transformation

Modify the OpenAI adaptor to respect the new setting when deciding whether to transform message roles.

Add Conditional Check in OpenAI Adaptor

Update the role transformation logic to check the channel setting before modifying message roles.

• Locate the role transformation block in relay/channel/openai/adaptor.go (around lines 326-332) within the request conversion function
• Wrap the existing role transformation logic with a conditional check that tests !info.ChannelSetting.DisableDeveloperRoleTransform
• Ensure the check is added at the outer level, before the model-specific prefix checks (o1-mini, o1-preview exclusions)
• Maintain the existing nested conditions for model-specific exclusions within the new outer check
• The transformation should only execute when: (1) the setting is not disabled AND (2) the model is a qualifying GPT-5/O-series variant AND (3) the first message has role "system"

🤖 Prompt for AI agents

Modify the OpenAI adaptor to check the new setting before transforming message
roles.

In `relay/channel/openai/adaptor.go`:
- Locate the role transformation block (around lines 326-332) in the request
conversion function
- Wrap existing role transformation logic with conditional check:
`!info.ChannelSetting.DisableDeveloperRoleTransform`
- Add check at outer level before model-specific prefix checks (o1-mini,
o1-preview exclusions)
- Maintain existing nested conditions for model-specific exclusions
- Transformation executes only when: setting is not disabled AND model is
qualifying GPT-5/O-series variant AND first message has role "system"

Phase 3: Documentation and Validation

Ensure the new setting is properly documented and can be configured through existing interfaces.

Verify Setting Integration

Confirm the new setting integrates correctly with the existing configuration management system.

• Verify that the ChannelSettings structure is properly loaded from the database via model/channel.go's GetSetting() method (this should be automatic due to JSON unmarshaling)
• Check that the UI channel configuration forms include the new field (may require frontend updates depending on how forms are generated)
• Add inline code comments in relay/channel/openai/adaptor.go explaining that the transformation can be disabled for upstream providers using legacy v1/chat/completions specification
• Consider adding a comment referencing the issue/ticket number for future maintainers

🤖 Prompt for AI agents

Validate integration and add documentation for the new setting.

- Verify `ChannelSettings` loads correctly from database via
`model/channel.go`'s `GetSetting()` method (automatic via JSON unmarshaling)
- Check UI channel configuration forms include the new field
- Add inline comments in `relay/channel/openai/adaptor.go` explaining the
transformation can be disabled for upstream providers using legacy
v1/chat/completions specification
- Add comment referencing the issue/ticket number for future maintainers

---

🚀 Next Steps

🤖 All AI agent prompts combined

Task: 1

Add a new channel-level configuration toggle to control role transformation
behavior.

In `dto/channel_settings.go`:
- Add `DisableDeveloperRoleTransform bool` field to `ChannelSettings` struct
with JSON tag `disable_developer_role_transform`
- Follow existing boolean flag patterns (e.g., `ForceFormat`,
`ThinkingToContent`)
- Add comment explaining this controls system→developer role transformation for
GPT-5 and O-series models
===============================================================================

Task: 2

Modify the OpenAI adaptor to check the new setting before transforming message
roles.

In `relay/channel/openai/adaptor.go`:
- Locate the role transformation block (around lines 326-332) in the request
conversion function
- Wrap existing role transformation logic with conditional check:
`!info.ChannelSetting.DisableDeveloperRoleTransform`
- Add check at outer level before model-specific prefix checks (o1-mini,
o1-preview exclusions)
- Maintain existing nested conditions for model-specific exclusions
- Transformation executes only when: setting is not disabled AND model is
qualifying GPT-5/O-series variant AND first message has role "system"
===============================================================================

Task: 3

Validate integration and add documentation for the new setting.

- Verify `ChannelSettings` loads correctly from database via
`model/channel.go`'s `GetSetting()` method (automatic via JSON unmarshaling)
- Check UI channel configuration forms include the new field
- Add inline comments in `relay/channel/openai/adaptor.go` explaining the
transformation can be disabled for upstream providers using legacy
v1/chat/completions specification
- Add comment referencing the issue/ticket number for future maintainers

💡 Iterate on the plan with: @coderabbitai <feedback>

Example Feedback
- @coderabbitai You can skip phase 3. Add a simple unit test case for phase 2.
- @coderabbitai For assumption 1 go ahead with option 3 and replan.

---

💬 Have feedback or questions? Drop into our discord!

[njzjz]

用参数覆盖改回system，实测可行。

{
  "operations": [
    {
      "path": "messages.0.role",
      "mode": "set",
      "value": "system",
      "conditions": [
        {
          "path": "messages.0.role",
          "mode": "prefix",
          "value": "developer"
        }
      ]
    }
  ]
}

[seefs001]

楼上的是个好法子