Skip to content

Refresh MiniMax preset to global endpoint and MiniMax-M3 - #1700

Open
octo-patch wants to merge 2 commits into
BigPizzaV3:mainfrom
octo-patch:octo/20260729-parameter-refresh-recvq95WPsHCC3
Open

Refresh MiniMax preset to global endpoint and MiniMax-M3#1700
octo-patch wants to merge 2 commits into
BigPizzaV3:mainfrom
octo-patch:octo/20260729-parameter-refresh-recvq95WPsHCC3

Conversation

@octo-patch

Copy link
Copy Markdown

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/v1https://api.minimax.io/v1 (global OpenAI-compatible endpoint).
  • websiteUrl / apiKeyUrl: point at the global platform host https://platform.minimax.io.
  • model (default): MiniMax-M2.7MiniMax-M3.
  • modelList: ["MiniMax-M2.7"]["MiniMax-M3", "MiniMax-M2.7"], so the previous model stays selectable.

The preset stays in the cn_official category (the vendor classification, matching the other first-class presets) and keeps the chatCompletions protocol. Adaptive reasoning is already applied to this provider through the existing chat reasoning routing keyed on the model name in crates/codex-plus-core/src/protocol_proxy.rs, so MiniMax-M3 is 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.

@BigPizzaV3

Copy link
Copy Markdown
Owner

维护者审查:当前改法会破坏现有中国区 MiniMax 用户的配置兼容性,暂不建议直接合并。

这个 PR 复用了现有 id = "minimax",把 api.minimaxi.com / platform.minimaxi.com 整体替换为国际区的 api.minimax.io / platform.minimax.io。但 MiniMax 的中国区和国际区账号、API Key 与服务入口是分区的;已有用户升级 Codex++ 后重新选择/应用同一个预设,会被静默切到另一区域,原有 Key 可能直接失效。与此同时该项仍标记为 category: "cn_official",与实际国际区入口也不一致。

建议:

  1. 保留现有 minimax 中国区预设及 api.minimaxi.com,只更新中国区实际可用的模型列表。
  2. 另加独立 ID(例如 minimax-global)的国际区预设,使用 api.minimax.io
  3. 分别补测试,固定两个预设的区域域名、分类和默认模型,避免后续再次互相覆盖。

这样既能加入 MiniMax-M3,也不会让现有用户在升级后跨区。

@octo-patch

Copy link
Copy Markdown
Author

Thanks for the review. I restored the existing minimax preset to the China endpoints, added a separate minimax-global preset, and added regional regression coverage. I ran node --test apps/codex-plus-manager/src/presets.test.ts and git diff --check.

@BigPizzaV3

Copy link
Copy Markdown
Owner

复审后确认,之前指出的区域兼容问题已经解决:现有 minimax 保留中国区入口,新增独立的 minimax-global 国际区预设,分类、默认模型和区域回归测试也一致。当前唯一阻塞是分支与最新 main 冲突;请 rebase/同步最新主线并重新跑 CI,冲突解决后可以继续合并评估。

@BigPizzaV3

Copy link
Copy Markdown
Owner

中国区 minimax 与独立 minimax-global 的拆分方案已经合理。请 rebase 当前 main,保留区域域名、分类和默认模型回归测试,并触发最新前端测试与三平台 CI;当前冲突状态不合并。

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants