Skip to content

v0.8.67 Docs: sync provider/model docs with Xiaomi MiMo UltraSpeed and Token Plan #3810

Description

@Hmbown

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

  • Docs list direct Xiaomi chat IDs: mimo-v2.5-pro, mimo-v2.5-pro-ultraspeed, and mimo-v2.5.
  • Docs list speech IDs separately and do not promote them as normal chat defaults.
  • /provider xiaomi-mimo ultraspeed and pro-ultraspeed are documented where shorthand examples are shown.
  • Token Plan key names and modes are documented consistently: Singapore default, China, Amsterdam, and pay-as-you-go.
  • Web provider facts/env tables include Token Plan env vars or intentionally explain why they are omitted.
  • Deprecated V2 names such as mimo-v2-flash are not promoted as current setup choices.

Related

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentationenhancementNew feature or requesttuiTerminal UI behavior, rendering, or interactionuxUser experience, interaction, or presentation polishv0.8.69Targeting v0.8.69

    Projects

    Status
    In progress

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions