> he trigger was watching deepseek-flash fail on the simplest /review run, every shellCommand and readFile call bouncing back with a raw zod issues blob, the model unable to recover because the error wasn't in a form it could read. by the end deepseek v4 pro was beating opus 4.7 6/10 times on our internal evals.

I think this is why Xiaomi forked OpenCode and created their own agent hardness, to reduce friction between model and harness:

https://github.com/XiaomiMiMo/MiMo-Code

probably yep, i doubt they'll be able to maintain that well. we did a lot of work improving MiMo's cache thrashing, it was pretty bad early on. Now we're seeing 97% cache rate on their models after lots of prefix work.