Skip to content

feat(providers): add MiMo V2.6 Pro and Flash to the Xiaomi Token Plan catalog - #15219

Merged
diegosouzapw merged 2 commits into
diegosouzapw:release/v3.8.52from
kang-heewon:feat/mimotp-v2.6-models
Oct 2, 2026
Merged

diegosouzapw merged 2 commits into
diegosouzapw:release/v3.8.52from
kang-heewon:feat/mimotp-v2.6-models

Conversation

@kang-heewon

@kang-heewon kang-heewon commented Sep 30, 2026 •

Copy link
Copy Markdown
Contributor

Summary

  • Add mimo-v2.6-pro and mimo-v2.6-flash to the xiaomi-mimo-token-plan (mimotp) catalog with Xiaomi's published limits: 1,048,576 context, 131,072 max output.
  • Xiaomi's Token Plan now serves the V2.6 pair and retires mimo-v2.5-pro / mimo-v2.5 at 2026-10-21 10:00 (Beijing time) (Token Plan models). Until now the catalog listed only the V2.5 pair, so the new models were missing from /v1/models and the dashboard model picker.
  • The V2.5 entries stay in place until Xiaomi retires them.
  • Vision already works for both IDs through the shared mimo-v2.6-pro / mimo-v2.6-flash vision fragments from fix(capabilities): resolve the MiMo v2.6 family as vision-capable (#14587) #14595, so this PR changes no capability logic.

Related Issues

Validation

  • Change type: provider
  • Focused tests and category gates from the golden path
    • node --import tsx/esm --test tests/unit/xiaomi-providers-registry.test.ts tests/unit/xiaomi-token-plan-regions.test.ts tests/unit/14587-mimo-v2-6-vision.test.ts tests/unit/xiaomi-mimo-token-plan-dispatcher-probe.test.ts: 48 passed, 0 failed
    • Every unit test that references xiaomi, mimo or CHAT_OPENAI_COMPAT_MODELS, plus models-catalog-* (1,413 tests): all pass under the node runner, except the two vitest-only tests/unit/autoCombo/* files, which fail the same way on the base commit. test:scoped flags shared.ts as a hub file, so the full suite is left to CI.
    • bun scripts/check/check-provider-consistency.ts: OK
    • npm run check:provider-assets: passed
    • tests/unit/provider-translate-path-golden.test.ts: the only local diff is the host OS in the Copilot user-agent (darwin vs linux); no xiaomi-mimo-token-plan entry changed
    • gen:provider-reference: the generated reference does not list per-provider models, so it has no catalog diff
  • eslint with the repo suppressions on the changed files: clean
  • Based on the current release/v3.8.52 tip
  • Production-code changes include an updated automated test in this PR

Live check against a real Token Plan key (Singapore cluster), through OmniRoute:

Request mimotp/mimo-v2.6-flash mimotp/mimo-v2.6-pro
Chat, streaming, thinking disabled 200 200
Chat, non-streaming 200 —
Image input (solid red PNG → "Red") 200 200
Tool call (get_weather) 200, tool call emitted 200, tool call emitted
Thinking enabled 200, reasoning_content streamed —

Tests Added Or Updated

  • tests/unit/xiaomi-providers-registry.test.ts: asserts that the Token Plan catalog exposes both V2.6 IDs with a 1M context and 128K output.

Coverage Notes

  • The production change is two static catalog entries in open-sse/config/providers/shared.ts. The updated registry test covers them directly.

Reviewer Notes

  • Only the Token Plan catalog changes. The pay-as-you-go xiaomi-mimo catalog was left alone because it could not be verified live here.

Copilot AI balanced review requested due to automatic review settings September 30, 2026 16:28

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

… catalog

Xiaomi's Token Plan now serves mimo-v2.6-pro and mimo-v2.6-flash
(1M context, 128K output) and retires mimo-v2.5-pro / mimo-v2.5 on
2026-10-21. The mimotp catalog only listed the v2.5 pair, so the new
models were missing from /v1/models and the dashboard picker.
@kang-heewon
kang-heewon force-pushed the feat/mimotp-v2.6-models branch from 01f72d8 to b8797c0 Compare September 30, 2026 17:25
@diegosouzapw
diegosouzapw merged commit b40e9a6 into diegosouzapw:release/v3.8.52 Oct 2, 2026
15 of 16 checks passed
@diegosouzapw

Copy link
Copy Markdown
Owner

Thanks @kang-heewon — merged into release/v3.8.52; it ships in the next release.

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.

3 participants