Repository navigation
Replies: 10 comments 1 reply
|
Hey @xspylol! Massive thanks for these five well-written requests — Qwen, Kimi, Z.ai/GLM, Xiaomi MiMo, and MiniMax. Bundling my reply since the architecture is the same for all of them. Quick status:
Adding each web-cookie provider is straightforward in principle but non-trivial in practice — each frontend uses a different streaming format (WS vs SSE), most use a PoW/captcha layer that needs reverse-engineering (the DeepSeek one already gave us a bug — see #2680 / #2724), and the cookie-extraction UX needs documentation per site. I have opened umbrella issue #2725 covering all five so we can prioritize them by upstream stability / model quality and tackle them one at a time. Suggested order there is Qwen Web → Kimi Web → GLM Web first (highest leverage given how generous their free web tiers are), then MiMo and MiniMax. If you have a different preference, drop a comment on #2725. |
|
Agreed, @richardchen874-sys -- those are exactly the fragility points that pushed MiMo to the back of the roadmap behind Qwen/Kimi/GLM in #2725. The instability cost of PoW/WS churn is higher than for a standard API provider, so it needs more upfront investment to be reliable for agentic loops. Will update here when MiMo moves up the queue. |
|
Agreed on all counts, @richardchen874-sys. Qwen/Kimi/GLM first for upstream stability, and when MiMo moves up #2725 it'll ship as an experimental provider first with explicit warnings around session expiry, streaming instability, and account safety -- exactly the framing you described. I'll ping here when it's queued. |
|
@xspylol — MiMo models are now available via the Antigravity CLI provider and other routes. Is the web cookie provider still needed, or has the upstream situation changed? Otherwise I will close this in 7 days for inactivity. |
|
Follow-up -- this is already tracked and shipped in #9951 (Xiaomi MiMo Web Cookie provider). Should be available in a recent release; if you don't see it, check your OmniRoute version. |
|
@xspylol A correction to my last reply: I said the Xiaomi MiMo Web Cookie provider was "tracked and shipped in #9951". That was wrong. The only MiMo providers today are API-key based ( The request stands, and this discussion stays open for it. |
|
i am also waiting for the web aistudio.xiaomimimo.com as its faster than the api in token plan |
|
Noted, @triggered02. I'm leaving this discussion open as the request for the MiMo AI Studio cookie provider. As described above, there's currently no provider for it, only the API-key MiMo providers. |
Uh oh!
There was an error while loading. Please reload this page.
Description
I would like to request a new Web Cookie Provider specifically for the Xiaomi MiMo Studio ecosystem (
https://aistudio.xiaomimimo.com).This would allow users to extract their browser session cookies from the MiMo Studio playground and use them to route mimo-v2.5-pro through OmniRoute for high-volume, local API access.
Why is this needed?
Xiaomi’s newly released MiMo-V2.5-Pro is a massive 1-trillion parameter MoE model with a 1-million token context window. It is specifically optimized for long-horizon agentic workflows and complex software engineering tasks (such as end-to-end compiler design).
While the official
platform.xiaomimimo.comdeveloper API has strict rate limits during its beta period, the web-based MiMo Studio (aistudio.xiaomimimo.com) is completely free to use with incredibly generous, browser-based boundaries.Adding a Web Cookie proxy for MiMo Studio would allow independent developers to route this powerhouse model directly into agentic CLIs (like Kilo Code, OpenCode, or Claude Code) via OmniRoute without hitting early token caps or requiring official corporate API verification.
How it could work:
aistudio.xiaomimimo.com).mimo-v2.5-pro(with support for the 1M context endpoints)./v1/chat/completionsrequest structure to match MiMo's web-socket/SSE streaming format.Thank you for the incredible work on OmniRoute! Having first-class web-session support for Xiaomi's massive new MoE models would be an amazing addition to the local development toolkit.
All reactions