You cannot run a new browser task on Xiaomi's original MiMo-V2-Pro API now: Xiaomi says mimo-v2-pro was automatically replaced with mimo-v2.5-pro from June 1, 2026, then deprecated on June 30. That replacement was also retired in October. Keep the old workflow as an archived baseline, but hand current work to a verified local agent and available model route. With Tabbit Browser, the human can sign into the two pages, use Tabbit CLI through a supported local client, compare the same record ID, and stop at a named draft for review. Xiaomi deprecation table · Tabbit CLI quick start
An older OpenClaw/KiloCode user called its speed and execution "very, very" impressive; another agent user reported OpenRouter rejected openrouter/xiaomi/mimo-v2-pro as an invalid model ID. Those reports are historical and don't establish availability now. OpenClaw discussion · Hermes Agent error report
Key takeaways
The exact Xiaomi model ID
mimo-v2-prois retired. Xiaomi's first-party schedule gives a June 1 replacement time and June 30 deprecation time, both UTC+8.The system first routed the original ID to V2.5 Pro, then later retired that generation too. Current requests under an old alias do not prove they reach the original model.
I could not verify a live third-party endpoint for exact
xiaomi/mimo-v2-proon November 10, 2026. The detail page is still reachable, but the public OpenRouter model listing returned no exact ID.Preserve a prompt, expected fields, and fixtures as an archived baseline. Label them as historical; don't claim an original-model test.
Tabbit CLI remains a separate local browser connector. Pick and verify an available model/client independently, sign in yourself, compare the two pages, and leave a named draft for review.
Availability check for the exact model
| Route checked | Evidence on November 10, 2026 | What it means |
|---|---|---|
| Xiaomi API | Official table: mimo-v2-pro replaced from June 1, deprecated June 30, 2026 UTC+8 | Original first-party ID is no longer a stable route to MiMo-V2-Pro |
| OpenRouter | Exact model listing query returned no xiaomi/mimo-v2-pro; detail page still renders generic model text without a current provider route | No current endpoint verified; a reachable page is not a successful API route |
| Model catalog | Models.dev record is a discovery pointer, not an API health check | Recheck the provider's live IDs and endpoint before selecting a model |
| Tabbit CLI | Separate browser tooling documented by Tabbit | It cannot restore model access; local agent, model route, CLI, and site session are separate |
Xiaomi's deprecation notice distinguishes system replacement from deprecation. From June 1, calls using the old ID were switched to mimo-v2.5-pro; at June 30, that old model name expired. Xiaomi later announced that V2.5 Pro requests were routed to V2.6 Pro from October 14, and the ID retired October 21. These are successive API changes, not proof that an old request still invokes the March V2 Pro model. This article is specifically about MiMo-V2-Pro, not its later generations.
Preserve the task as an archived baseline
If you have an old prompt or task record, retain it with the requested model ID, date, client, expected fields, and source URLs. Mark the execution result unavailable unless you have a dated transcript that proves which model served the request. A prompt can preserve the intended procedure; it cannot preserve a retired endpoint or guarantee the original behavior.
For a new run, select an available model route explicitly in a local agent client and verify the returned model ID. The provider decision is separate from the browser connector. Tabbit's CLI quick start explains skill installation and browser login for its supported clients. Pi uses /skill:tabbit; other clients may use /tabbit, /skills, or automatic skill loading. Confirm skill discovery, local tabbit-cli launcher access, and the website session as separate checks. See the complete Tabbit CLI guide, existing-browser connection guide, and MCP versus CLI comparison.
Compare the same record in two authorized pages
The example below is an illustrative human-reviewed handoff, not a MiMo-V2-Pro execution. It assumes that you have permission to read both pages and that a currently available local agent/model has already passed its own setup check. If not, perform the comparison yourself in Tabbit Browser.
Use the currently configured local agent and Tabbit skill. The archived MiMo-V2-Pro route is retired; do not claim this task ran on MiMo-V2-Pro. In a separate task tab, open only the two workspace pages I name. Find record GEO-191 in each page. Record each URL, visible title, timestamp or version, and the fields shown for that same ID. Do not edit either record or follow unrelated links. Mark missing, changed, or inaccessible fields as unknown.
Create a draft named "MiMo V2-Pro record comparison — GEO-191" in the selected workspace. Include one row per page, a field-by-field comparison, source links, and open questions. Label the archived model route as unavailable. Do not publish or share. Stop and show me the draft for review.
Expected output: draft link, workspace name, two source URLs with GEO-191, matching/different fields, unknowns, and an explicit note that the retired MiMo-V2-Pro route was not used.GEO-191 is a sample record and draft name, not a real workspace item. Keep credentials out of the draft. Check that both pages show the same stable ID before comparing fields. If one page has a different ID, stop rather than merging the records. Use the first browser task checklist to keep the first live run read-only.
Decide whether to run, hand off, or stop
| What you can verify | Action |
|---|---|
| Only an archived prompt or model card remains | Preserve it as a historical baseline; no live MiMo-V2-Pro task claim |
| A provider lists another current model ID | Test that exact route and record the returned ID before authorizing browser tools |
| A local agent and Tabbit CLI are available, but no verified model route is selected | Use a human handoff or wait; browser connectivity does not replace model access |
| The two pages show the same record ID and readable fields | Save a cited comparison draft and review each value yourself |
| The IDs differ, a page is inaccessible, or a field lacks evidence | Stop, mark the difference or unknown, and request access or clarification |
For setup paths, see Codex Tabbit CLI setup, agent browser setup, browser automation agents, and browser agent security risks. Codex browser versus Tabbit CLI covers connector choice, while web search versus browser control explains why public search cannot confirm signed-in workspace data.
FAQ
Can I still use Xiaomi's MiMo-V2-Pro API?
No. Xiaomi's deprecation table says the `mimo-v2-pro` ID was replaced by `mimo-v2.5-pro` from June 1, 2026 and deprecated at 00:00 UTC+8 on June 30. The replacement was itself retired in October, so do not assume an old ID reaches the original model.
Can I use the old MiMo-V2-Pro model through OpenRouter?
I could not verify a live OpenRouter endpoint for the exact `xiaomi/mimo-v2-pro` ID on November 10, 2026. The model page remains reachable, but the public model listing did not return that exact ID. Recheck provider data before relying on any route.
Does an archived MiMo-V2-Pro prompt still work?
It can preserve the intended steps and output schema, but it does not restore the retired model or its behavior. Treat it as a test fixture or handoff checklist and label the model and execution route as unavailable.
Can Tabbit CLI connect to my signed-in browser without MiMo-V2-Pro?
Tabbit CLI is a separate browser connector. A local agent still needs an available model route and permission to run local tools; then it can use the Tabbit Browser environment where you signed into the site.
How do I check the same record in two signed-in pages?
Open both authorized pages in Tabbit Browser and ask the local agent to compare the stable record ID, capture each page URL and visible title, and note which fields agree or differ. Stop at a named draft for human review.
Should I replace MiMo-V2-Pro with a newer MiMo version automatically?
No. Xiaomi's replacement dates and later retirement notices show that the same API ID may route to different versions over time. Choose and verify a currently available model explicitly, then rerun the task checks before using it.