Skip to content

代码minimax token plan问题 #1013

Description

@shook2012
Image Image

代理minimax时,再如果在命令行直接使用claude code cli,就总是返回503,总是被熔断。但通过vs code插件使用claude code,就不存在这个问题。

如果我直连minimax baseurl,在命令行使用或vs code中使用都正常。

这是什么问题呢?

Activity

  1. ding113 commented on Apr 13, 2026

    @ding113
    Owner

    未复现这个问题,请提供更详细的日志

  2. shook2012 commented on Apr 14, 2026

    @shook2012
    Author

    尝试: Minimax-6
    +239ms
    HTTP 400

    Provider ID: 11
    端点
    https://api.minimaxi.com/anthropic
    熔断器:
    closed
    4/5 次失败
    错误
    Provider Minimax-6 returned 400: invalid_request_error: invalid params | Upstream: {"type":"error","error":{"type":"invalid_request_error","message":"invalid params"}}

    重试 #2
    +429ms
    HTTP 400

    Provider ID: 11
    端点
    https://api.minimaxi.com/anthropic
    熔断器:
    closed
    4/5 次失败
    错误
    Provider Minimax-6 returned 400: invalid_request_error: invalid params | Upstream: {"type":"error","error":{"type":"invalid_request_error","message":"invalid params"}}

    尝试: Minimax-7
    +1924ms
    HTTP 400

    Provider ID: 10
    端点
    https://api.minimaxi.com/anthropic
    熔断器:
    closed
    4/5 次失败
    错误
    Provider Minimax-7 returned 400: invalid_request_error: invalid params | Upstream: {"type":"error","error":{"type":"invalid_request_error","message":"invalid params"}}

  3. shook2012 commented on Apr 14, 2026

    @shook2012
    Author

    claude-code-hub-app-hmat | {"level":"warn","time":"2026-04-14T11:02:26.809Z","pid":1,"hostname":"dbeba867c29a","providerId":1,"providerName":"Aliyun","statusCode":400,"statusCodeInferred":false,"error":"Provider Aliyun returned 400: Provider returned 400: Bad Request | Upstream: {"error":{"code":"InvalidParameter","message":"Error code: 400 - {'error': {'message': '<400> InternalError.Algo.InvalidParameter: Range of max_tokens should be [1, 65536]', 'type': 'invalid_request_error', 'param': None, 'code': 'invalid_parameter_error'}, 'id': 'chatcmpl-6b0965eb-8625-4fb4-af6e-1b9d6eb29ebe', 'request_id': '6b0965eb-8625-4fb4-af6e-1b9d6eb29ebe'}","param":null,"type":null},"request_id":"c8d95b10-75b9-9660-99bb-b8cfceae4972"}","attemptNumber":2,"totalProvidersAttempted":1,"willRetry":false,"msg":"ProxyForwarder: Provider error occurred"}

    是因为max-tokens使用了遵循客户端请求?

  4. shook2012 commented on Apr 14, 2026

    @shook2012
    Author

    但我刚刚我所有的minimax的套餐配置都调整成了64000,还是同样的错呐

  5. shook2012 commented on Apr 14, 2026

    @shook2012
    Author
    Image
  6. shook2012 commented on Apr 14, 2026

    @shook2012
    Author

    提一个问题,几乎我所有的minimax2.7 token plan都会轮一次。 只有一次成功,其它都失败.

  7. ding113 commented on Apr 14, 2026

    @ding113
    Owner

    请向 minimax 方面反馈。

  8. cwt9562 commented on Apr 15, 2026

    @cwt9562

    我这边发现,在claude code里配置 --model MiniMax-M2.7-highspeed 是可以的
    但是如果没配置,在CCH里通过模型重定向配置 haiku --> MiniMax-M2.7-highspeed 后,就会503
    看了下,好像调minimax接口时传的模型是claude-haiku-4-5-20251001

    Image

    [0000ms] 首次选择供应商

    系统状态:
    总供应商数: 2 个
    已启用 claude 类型: 1 个
    用户分组 default: 1 个
    健康检查通过: 1 个

    被过滤:
    💰 Kimi-coding-plan (provider-chain.filterDetails.不支持模型 claude-haiku-4-5-20251001)

    优先级 0 的候选供应商(1 个):
    • Minimax-coding-plan: 权重=1 成本=1 概率=1%

    ✓ 选择: Minimax-coding-plan

    等待请求结果...

    [0238ms] 请求失败(第 1 次尝试)

    供应商: Minimax-coding-plan
    状态码: 400
    错误: invalid_request_error: invalid params
    请求耗时: 238ms

    熔断状态:
    当前状态: 关闭(正常)
    失败次数: 2/99999
    距离熔断还有 99997 次

    错误详情:
    {
    "type": "error",
    "error": {
    "type": "invalid_request_error",
    "message": "invalid params"
    }
    }
    请求详情(用于排查问题):
    请求方法: POST
    请求 URL: http://0.0.0.0:3000/v1/messages?beta=true
    请求头:
    accept: application/json
    accept-encoding: gzip, deflate, br, zstd
    anthropic-beta: interleaved-thinking-2025-05-14,context-management-2025-06-27,prompt-caching-scope-2026-01-05,structured-outputs-2025-12-15
    anthropic-dangerous-direct-browser-access: true
    anthropic-version: 2023-06-01
    authorization: Bearer sk-a******060b
    connection: keep-alive
    content-length: 1712
    content-type: application/json
    host: localhost:23000
    user-agent: claude-cli/2.1.109 (external, claude-vscode)
    x-app: cli
    x-claude-code-session-id: d0eed943-7b85-4e00-a807-fb60e7308120
    x-forwarded-for: 172.18.0.1
    x-forwarded-host: localhost:23000
    x-forwarded-port: 3000
    x-forwarded-proto: http
    x-stainless-arch: x64
    x-stainless-lang: js
    x-stainless-os: Windows
    x-stainless-package-version: 0.81.0
    x-stainless-retry-count: 0
    x-stainless-runtime: node
    x-stainless-runtime-version: v24.3.0
    x-stainless-timeout: 600
    请求体:
    {
    "model": "claude-haiku-4-5-20251001",
    "messages": [
    0
    ],
    "system": [
    0,
    0,
    0
    ],
    "tools": [],
    "metadata": {
    "user_id": "{"device_id":"babdc0f921afcdc58be6aa035167cfb707f588aca9b642b02209f93a6f8cdec8","account_uuid":"","session_id":"d0eed943-7b85-4e00-a807-fb60e7308120"}"
    },
    "max_tokens": 32000,
    "temperature": 1,
    "output_config": {
    "format": {
    "type": "json_schema",
    "schema": {
    "type": "object",
    "properties": {...

    [0438ms] 请求失败(第 2 次尝试)

    供应商: Minimax-coding-plan
    状态码: 400
    错误: invalid_request_error: invalid params
    请求耗时: 200ms

    熔断状态:
    当前状态: 关闭(正常)
    失败次数: 2/99999
    距离熔断还有 99997 次

    错误详情:
    {
    "type": "error",
    "error": {
    "type": "invalid_request_error",
    "message": "invalid params"
    }
    }
    请求详情(用于排查问题):
    请求方法: POST
    请求 URL: http://0.0.0.0:3000/v1/messages?beta=true
    请求头:
    accept: application/json
    accept-encoding: gzip, deflate, br, zstd
    anthropic-beta: interleaved-thinking-2025-05-14,context-management-2025-06-27,prompt-caching-scope-2026-01-05,structured-outputs-2025-12-15
    anthropic-dangerous-direct-browser-access: true
    anthropic-version: 2023-06-01
    authorization: Bearer sk-a******060b
    connection: keep-alive
    content-length: 1712
    content-type: application/json
    host: localhost:23000
    user-agent: claude-cli/2.1.109 (external, claude-vscode)
    x-app: cli
    x-claude-code-session-id: d0eed943-7b85-4e00-a807-fb60e7308120
    x-forwarded-for: 172.18.0.1
    x-forwarded-host: localhost:23000
    x-forwarded-port: 3000
    x-forwarded-proto: http
    x-stainless-arch: x64
    x-stainless-lang: js
    x-stainless-os: Windows
    x-stainless-package-version: 0.81.0
    x-stainless-retry-count: 0
    x-stainless-runtime: node
    x-stainless-runtime-version: v24.3.0
    x-stainless-timeout: 600
    请求体:
    {
    "model": "claude-haiku-4-5-20251001",
    "messages": [
    0
    ],
    "system": [
    0,
    0,
    0
    ],
    "tools": [],
    "metadata": {
    "user_id": "{"device_id":"babdc0f921afcdc58be6aa035167cfb707f588aca9b642b02209f93a6f8cdec8","account_uuid":"","session_id":"d0eed943-7b85-4e00-a807-fb60e7308120"}"
    },
    "max_tokens": 32000,
    "temperature": 1,
    "output_config": {
    "format": {
    "type": "json_schema",
    "schema": {
    "type": "object",
    "properties": {...

  9. cwt9562 commented on Apr 16, 2026

    @cwt9562

    我又重新试了下,发现问题在于request body里的 output_config 属性
    我试着用apifox重放请求,发现将output_config:{}删了,就可以
    @ding113 这个参数是cch追加的,还是claudecode原本就有的?
    "output_config": {
    "format": {
    "type": "json_schema",
    "schema": {
    "type": "object",
    "properties": {
    "title": {
    "type": "string"
    }
    },
    "required": [
    "title"
    ],
    "additionalProperties": false
    }
    }

  10. ding113 commented on Apr 16, 2026

    @ding113
    Owner

    我又重新试了下,发现问题在于request body里的 output_config 属性
    我试着用apifox重放请求,发现将output_config:{}删了,就可以
    @ding113 这个参数是cch追加的,还是claudecode原本就有的?
    "output_config": {
    "format": {
    "type": "json_schema",
    "schema": {
    "type": "object",
    "properties": {
    "title": {
    "type": "string"
    }
    },
    "required": [
    "title"
    ],
    "additionalProperties": false
    }
    }

    cch默认情况下不会修改请求体内容

  11. cwt9562 commented on Apr 16, 2026

    @cwt9562

    我又重新试了下,发现问题在于request body里的 output_config 属性
    我试着用apifox重放请求,发现将output_config:{}删了,就可以
    @ding113 这个参数是cch追加的,还是claudecode原本就有的?
    "output_config": {
    "format": {
    "type": "json_schema",
    "schema": {
    "type": "object",
    "properties": {
    "title": {
    "type": "string"
    }
    },
    "required": [
    "title"
    ],
    "additionalProperties": false
    }
    }

    cch默认情况下不会修改请求体内容

    好的,那就是minimax官方要修复这个问题了

  12. shook2012 commented on Apr 17, 2026

    @shook2012
    Author

    claude code cli + minimax 直连没任何问题~ claude code cli + claude code hub + minimax就总是熔断,这就说不通了呀。

  13. shook2012 commented on Apr 17, 2026

    @shook2012
    Author

    [0199ms] 请求失败(第 1 次尝试)

    供应商: Minimax-9
    状态码: 400
    错误: invalid_request_error: invalid params
    请求耗时: 199ms

    熔断状态:
    当前状态: 关闭(正常)
    失败次数: 4/5
    距离熔断还有 1 次

    错误详情:
    {
    "type": "error",
    "error": {
    "type": "invalid_request_error",
    "message": "invalid params"
    }
    }
    请求详情(用于排查问题):
    请求方法: POST
    请求 URL: http://0.0.0.0:23000/v1/messages?beta=true
    请求头:
    accept: application/json
    accept-encoding: gzip, deflate
    accept-language: *
    anthropic-beta: claude-code-20250219,interleaved-thinking-2025-05-14,context-management-2025-06-27,prompt-caching-scope-2026-01-05,effort-2025-11-24
    anthropic-dangerous-direct-browser-access: true
    anthropic-version: 2023-06-01
    authorization: Bearer sk-a******c410
    connection: keep-alive
    content-length: 1523
    content-type: application/json
    host: 10.192.56.61:23000
    sec-fetch-mode: cors
    user-agent: claude-cli/2.1.87 (external, cli)
    x-app: cli
    x-claude-code-session-id: 814ecaa7-a55a-4c33-8b38-8ae6c8273fd6
    x-forwarded-for: 192.168.13.54
    x-forwarded-host: 10.192.56.61:23000
    x-forwarded-port: 23000
    x-forwarded-proto: http
    x-stainless-arch: x64
    x-stainless-lang: js
    x-stainless-os: Windows
    x-stainless-package-version: 0.74.0
    x-stainless-retry-count: 0
    x-stainless-runtime: node
    x-stainless-runtime-version: v22.22.0
    x-stainless-timeout: 600
    请求体:
    {
    "model": "MiniMax-M2.7",
    "messages": [
    0
    ],
    "system": [
    0,
    0,
    0
    ],
    "tools": [],
    "metadata": {
    "user_id": "{"device_id":"274e4b8cda8e4ee1e7d92fef2f6923f3e70df29c6a98eaa597a1cbfe7bf7776e","account_uuid":"","session_id":"814ecaa7-a55a-4c33-8b38-8ae6c8273fd6"}"
    },
    "max_tokens": 32000,
    "temperature": 1,
    "output_config": {
    "effort": "medium",
    "format": {
    "type": "json_schema",
    "schema": {
    "type": "object",
    "pro...

    [0376ms] 请求失败(第 2 次尝试)

    供应商: Minimax-9
    状态码: 400
    错误: invalid_request_error: invalid params
    请求耗时: 177ms

    @ding113 大佬,帮忙看下能看出问题么?

  14. added
    oncallCritical blocking issue requiring immediate oncall attention
    on Apr 20, 2026
  15. liujiliang2008 commented on Apr 24, 2026

    @liujiliang2008

    同样遇到了这个问题,求解? @shook2012 请问解决了么?

  16. szh1118 commented on May 2, 2026

    @szh1118

    遇到了相同的问题

  17. szh1118 commented on May 4, 2026

    @szh1118

    @ding113 我遇到了同样的问题,经过对比测试发现:

    问题不在 Minimax,而在 CCH 的转发逻辑:

    1. 直接使用 Minimax 官方 baseURL(Anthropic API 格式)

      • Claude Code 中使用 agent ✅ 正常,无任何 503 问题
    2. 通过 CCH 转发 Minimax 官方 baseURL

      • Claude Code 中使用 agent ❌ 稳定出现 503错误

    这明确证明问题出在 CCH 的请求转发或熔断机制上,而不是 Minimax 的 API 兼容性问题。

    建议:

    • 请检查 CCH 在转发请求时是否正确处理了请求头、参数或超时配置
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:providerbugSomething isn't workingoncallCritical blocking issue requiring immediate oncall attention

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions