Refresh MiniMax preset to global endpoint and MiniMax-M3 - #1700
Refresh MiniMax preset to global endpoint and MiniMax-M3#1700octo-patch wants to merge 2 commits into
Conversation
|
维护者审查:当前改法会破坏现有中国区 MiniMax 用户的配置兼容性,暂不建议直接合并。 这个 PR 复用了现有 建议:
这样既能加入 MiniMax-M3,也不会让现有用户在升级后跨区。 |
|
Thanks for the review. I restored the existing |
|
复审后确认,之前指出的区域兼容问题已经解决:现有 |
|
中国区 minimax 与独立 minimax-global 的拆分方案已经合理。请 rebase 当前 main,保留区域域名、分类和默认模型回归测试,并触发最新前端测试与三平台 CI;当前冲突状态不合并。 |
Reason: Refresh the first-class MiniMax provider preset to the global endpoint and its current model lineup.
What changed
apps/codex-plus-manager/src/presets.ts— the built-in MiniMax preset:baseUrl:https://api.minimaxi.com/v1→https://api.minimax.io/v1(global OpenAI-compatible endpoint).websiteUrl/apiKeyUrl: point at the global platform hosthttps://platform.minimax.io.model(default):MiniMax-M2.7→MiniMax-M3.modelList:["MiniMax-M2.7"]→["MiniMax-M3", "MiniMax-M2.7"], so the previous model stays selectable.The preset stays in the
cn_officialcategory (the vendor classification, matching the other first-class presets) and keeps thechatCompletionsprotocol. Adaptive reasoning is already applied to this provider through the existing chat reasoning routing keyed on the model name incrates/codex-plus-core/src/protocol_proxy.rs, soMiniMax-M3is covered without further change. Per-model context windows continue to be configured through the shared model-window editor, consistent with every other preset in this file.Checks
npm run check(tsc --noEmit -p tsconfig.json) — passed.npm run vite:build— passed.Note:
npm test(node --test) targets Node 22's native TypeScript support (as used in CI); it could not be exercised in the local Node 20 environment. The change is a static preset-data update covered by the type-check and production build above.