why can't use alibaba coding plan ?

[jomyhuang]

Client or integration

Codex CLI

Area

CLI

Summary

why can't use alibaba coding plan (china)?
I fix base URL to https://coding.dashscope.aliyuncs.com/v1
still doesn't work...

Reproduction

new provider from alibaba coding plan (intl.)
fix base URL: https://coding.dashscope.aliyuncs.com/v1
error 401, key is work in my cc-switch.

Version

2.7.43

Operating system

Windows 11

Provider and model

alibaba/qwen3.7-plus

Logs or error output

Screenshots and supporting files

No response

Redacted configuration

Checks

• I searched existing issues and documentation.
• I removed secrets, tokens, account details, request credentials, and personal data.

Translated Message

Original language: Chinese

客户端或集成

Codex CLI

区域

CLI

概要

为什么不能使用阿里巴巴编码计划（中国）？
我将基础 URL 修复为 https://coding.dashscope.aliyuncs.com/v1 仍然不起作用……

复现

来自阿里巴巴编码计划（intl.）的新提供商。
修复基础 URL: https://coding.dashscope.aliyuncs.com/v1
错误 401，密钥在我的 cc-switch 中正常工作。

版本

2.7.43

操作系统

Windows 11

提供商和模型

alibaba/qwen3.7-plus

日志或错误输出

截图和支持文件

无响应

涂黑的配置

检查

• 我搜索了现有的问题和文档。
• 我删除了秘密、令牌、账户详细信息、请求凭证和个人数据。

[github-actions]

_{Automated translation bookkeeping — detected language: unknown.}

[Wibias]

[shipping-github] Research review

Claim: Alibaba Coding Plan (China) does not work — 401 after pointing base URL at coding.dashscope.aliyuncs.com/v1.
Checked against: dev@be177ea5

Field	Finding
Still an issue on latest development?	unclear (insufficient repro detail) / likely config-region mismatch still possible
Exact issue	Built-in alibaba preset uses intl coding-intl.dashscope.aliyuncs.com; China Coding Plan host is not a first-class choice; 401 with a key that works elsewhere
Fixed on development?	no dedicated China Coding Plan preset/fix found
Open PR covering this?	none
Duplicate of?	related closed #457/#200 (baseUrl override / region migration for token-plan); not the same Coding Plan China host
Security relevance	none — n/a
Priority	middle — blocks China Coding Plan users; needs auth/header/region clarification
Verdict	Needs fix on development (and/or docs); currently Not actionable without redacted request headers / exact provider id

Evidence: src/providers/registry.ts alibaba → https://coding-intl.dashscope.aliyuncs.com/v1. No coding.dashscope.aliyuncs.com preset. Token-plan China/intl are separate entries.
Gaps: No logs, auth header shape, or confirmation whether override stuck vs silent registry rewrite. Ask reporter for ocx provider show and a redacted 401 body.

[Wibias]

[shipping-github] Opened PR #776 to address this.

[jomyhuang]

it's work after new custom provider.

[Wibias]

Thanks @jomyhuang — this is fixed by PR #776 by adding China / International / Custom base URL choices for Alibaba Coding Plan.