Affected area
None
What problem are you trying to solve?
CCS already includes qwen and alibaba-coding-plan profiles, but the user-facing platform name, official API-key page, endpoints, plans, and model references are moving to QwenCloud. Keeping only the older branding can make users choose the wrong official entry point, while replacing existing profile IDs could break saved configurations.
Proposed solution or direction
Please help choose the backward-compatible path: (1) rename only the user-visible provider while preserving existing IDs; (2) add QwenCloud as an alias/preset while retaining the old profiles; or (3) add a separate QwenCloud preset if the endpoint or plan behavior requires it. The QwenCloud team can provide approved copy, icons, validated endpoints, recommended models, and regression support after the preferred path is confirmed.
Suggested user flow
- Existing users keep their saved qwen / alibaba-coding-plan configuration working.
- New users can identify QwenCloud directly in CCS.
- The provider entry links to the current QwenCloud API-key, documentation, model, and pricing pages.
Alternatives considered
A hard rename of configuration IDs risks breaking existing references. A duplicate implementation may create long-term maintenance drift. We prefer the smallest compatible migration recommended by the maintainers.
Additional context
Official references:
QwenCloud contact: Jialing / QwenCloud Product Manager / https://github.com/evelyn-jialin-zhang
Before submitting
Affected area
None
What problem are you trying to solve?
CCS already includes qwen and alibaba-coding-plan profiles, but the user-facing platform name, official API-key page, endpoints, plans, and model references are moving to QwenCloud. Keeping only the older branding can make users choose the wrong official entry point, while replacing existing profile IDs could break saved configurations.
Proposed solution or direction
Please help choose the backward-compatible path: (1) rename only the user-visible provider while preserving existing IDs; (2) add QwenCloud as an alias/preset while retaining the old profiles; or (3) add a separate QwenCloud preset if the endpoint or plan behavior requires it. The QwenCloud team can provide approved copy, icons, validated endpoints, recommended models, and regression support after the preferred path is confirmed.
Suggested user flow
Alternatives considered
A hard rename of configuration IDs risks breaking existing references. A duplicate implementation may create long-term maintenance drift. We prefer the smallest compatible migration recommended by the maintainers.
Additional context
Official references:
QwenCloud contact: Jialing / QwenCloud Product Manager / https://github.com/evelyn-jialin-zhang
Before submitting