Problem
Code already exposes Xiaomi MiMo V2.5 options more completely than several docs surfaces do. The direct Xiaomi provider/model picker includes mimo-v2.5-pro, mimo-v2.5-pro-ultraspeed, and mimo-v2.5; /provider xiaomi-mimo ultraspeed and pro-ultraspeed expand to mimo-v2.5-pro-ultraspeed.
Some docs still lag behind that behavior, which makes setup feel unreliable when a user asks whether UltraSpeed exists.
Stale or incomplete surfaces found
config.example.toml: the global model examples and [providers.xiaomi_mimo] section list mimo-v2.5-pro and mimo-v2.5, but omit mimo-v2.5-pro-ultraspeed in at least the direct-provider chat list.
config.example.toml: Xiaomi credential comments should mention Token Plan env vars and mode values consistently, not only the generic API key/model path.
docs/CONFIGURATION.md: the provider/model reference says direct Xiaomi recognizes mimo-v2.5-pro and mimo-v2.5, but omits mimo-v2.5-pro-ultraspeed.
docs/CONFIGURATION.md: Xiaomi Token Plan region docs mention China explicitly, but code supports Singapore default, China, and Amsterdam modes.
web/scripts/facts-lib.mjs, web/lib/facts-drift.ts, and generated web facts list Xiaomi env vars without the Token Plan key names.
docs/rfcs/HARNESS_PROFILE_CUTLINE.md still says Xiaomi MiMo V2.5 Pro / Flash; use current V2.5 naming or mark it historical.
Acceptance criteria
Related
Problem
Code already exposes Xiaomi MiMo V2.5 options more completely than several docs surfaces do. The direct Xiaomi provider/model picker includes
mimo-v2.5-pro,mimo-v2.5-pro-ultraspeed, andmimo-v2.5;/provider xiaomi-mimo ultraspeedandpro-ultraspeedexpand tomimo-v2.5-pro-ultraspeed.Some docs still lag behind that behavior, which makes setup feel unreliable when a user asks whether UltraSpeed exists.
Stale or incomplete surfaces found
config.example.toml: the global model examples and[providers.xiaomi_mimo]section listmimo-v2.5-proandmimo-v2.5, but omitmimo-v2.5-pro-ultraspeedin at least the direct-provider chat list.config.example.toml: Xiaomi credential comments should mention Token Plan env vars and mode values consistently, not only the generic API key/model path.docs/CONFIGURATION.md: the provider/model reference says direct Xiaomi recognizesmimo-v2.5-proandmimo-v2.5, but omitsmimo-v2.5-pro-ultraspeed.docs/CONFIGURATION.md: Xiaomi Token Plan region docs mention China explicitly, but code supports Singapore default, China, and Amsterdam modes.web/scripts/facts-lib.mjs,web/lib/facts-drift.ts, and generated web facts list Xiaomi env vars without the Token Plan key names.docs/rfcs/HARNESS_PROFILE_CUTLINE.mdstill says Xiaomi MiMo V2.5 Pro / Flash; use current V2.5 naming or mark it historical.Acceptance criteria
mimo-v2.5-pro,mimo-v2.5-pro-ultraspeed, andmimo-v2.5./provider xiaomi-mimo ultraspeedandpro-ultraspeedare documented where shorthand examples are shown.mimo-v2-flashare not promoted as current setup choices.Related
docs/evidence/xiaomi-mimo-2026-06-23/