Re:Xiaomi MiMo v2.6
by pkulak on Monday September 21, 2026 @08:24PM
(#49795264)
4.1 consistently surprises me in capability for the price. And I don't think I'm the only one. It's been dominating the leaderboard at OpenRouter, and I just got an email today from Fireworks saying they were _raising_ the price by about 30%. I'll probably switch, because their infra doesn't support being the highest-cost, but it's still telling.
[ Parent
| on HN ]
I tried it a few times and liked the speed, but often found it ended up looping, i.e. repeating the same token sequence (e.g. the same sequence of 5 paragraphs) over and over again until it hit the max output limit. This doesn't end up happening every session, but does every now and then.
My impression of DSv4.1-flash was very positive aside from this. But that was enough for me to stick with GLM-5.3(-flash), which both gave me consistently great results
I was using a vibe coded bare bones harness. I was wondering if this was normal from DSv4.1-flash, or if its my harnesses fault.
I've had that looping issue with open models too. But never 4.1. I wonder if it's a model + harness combo? But yeah, one loop issue and I'm done with a model forever.
Harness. Especially if a tool call error doesn't say what to do next and the model is not RL'd with that tool, a retry storm is common.
So if you use MCP a lot, simplify the params, be more lenient on validation and rework the errors.
It is quite good with shell.
Yeah, that's what I'd been leaning towards.
No mcp, but I'll see if I can reproduce and debug it, since other people don't seem to have that problem as badly as I've experienced it (and the idea of having a nasty bug like that bothers me).
No mcp support. I'll try copying deepseek harness's basic tool call formats as a starting point.