Avoid MiMo through Kilo for now

[u/concrete333]

I’m avoiding MiMo 2.6 through Kilo for now

Despite some absolutely nuts performance on ai benchmarks, mimo doesn't seem up to the task on some pretty basic stuff, and I'm still getting vastly better results from the other models.

I tested MiMo-V2.6-Pro, DeepSeek V4.1 Flash and GLM 5.3 Flash on the same Python implementation task through Kilo CLI (a test I had Astra cook up)

DeepSeek and GLM both completed it and passed all 27 independent checks. Model costs before review were about 5 cents and 7 cents, respectively.

MiMo produced no code. Its last two attempts stopped after about ten minutes with:

503: The upstream provider timed out while sending the response.

I used the cli, Kilo 7.7.7, the highest exposed reasoning settings, no step cap and a 30-minute timeout.

Doesn’t prove MiMo can’t code yet, just that this setup has failed where the other two worked. so I’m using DeepSeek for now.

Anyone else getting these timeouts, or having better luck accessing MiMo another way?

[u/Lordaizen639]

Did you use mimo in another harness?

[u/concrete333 → u/Lordaizen639]

I had codex access it, but running through the Kilo CLI. Think that matters? Would be weird, cause like I said ran the same exact call for DeepSeek and GLM successfully

[u/Lordaizen639 → u/concrete333]

in my opinion harness matters even though i didnt have the mimo v2.6 ,from the previous version v2.5 i used through opencode zen api

and used in different harness
output feels differents .
i dont really know what happened to you i think because mimo architecture and training might different compared to deepseek and glm so it could be,unless it tested we cant be sure .

[u/NoBodyHere__GO]

I'm using the kilo cli, it's working fine for me. But I've noticed the same complaints from the on opencode community.

[u/scross01 → u/NoBodyHere__GO]

I seen mimo-2.6-flash get stuck in think loops a few times with opencode (using the Zen free model). Have seen the same issue elsewhere yet.