Mistral-Next 22B vs oh-my-codex (OMX)

“The primitive here is clean: 22B dense weights, Apache 2.0, download and run. No handshake with a vendor runtime, no special SDK required — just HuggingFace transformers or llama.cpp and you're live. The DX bet is maximum portability over managed convenience, which is the right call for this audience. Apache 2.0 is the specific technical decision that earns the ship — MIT-adjacent permissiveness means you can actually build a product on this without a lawyer reading the license, unlike Llama's historical custom terms.”

“If you use OpenAI Codex CLI daily, OMX is an immediate productivity upgrade. Structured $deep-interview → $ralplan → $team workflows mean Codex actually understands the codebase before writing, and isolated git worktrees for parallel specialists eliminate the merge conflicts that kill multi-agent coding sessions.”

“Direct competitor is Llama 4 Scout, and the honest comparison comes down to: does the benchmark delta justify a model switch for teams already on Llama? The multilingual reasoning claims need independent replication — Mistral's own benchmarks are Mistral's own benchmarks. What kills this in 12 months isn't a competitor, it's model commoditization: at sub-30B, inference is cheap enough that the winning model becomes whichever one the cloud providers optimize hardest, and AWS and Google will optimize for Llama first. Still, Apache 2.0 with genuine sub-30B multilingual performance is a real thing that exists, and that's worth shipping.”

“This is a power-user wrapper on Codex CLI, which itself is still early-stage software. You're now debugging two layers of abstraction when things break. The hook system is clever but brittle — and the project is maintained by one developer. Evaluate your risk tolerance before making this a team dependency.”

“The thesis here is specific: by 2027, most inference happens on-device or in private VPCs, not in hyperscaler APIs, and the model that wins that world is the one with the least restrictive license and the smallest footprint that clears the quality bar. Mistral is betting on sovereign compute and edge inference scaling faster than frontier model improvement — that's a falsifiable claim and it's not obviously wrong. The second-order effect that matters: Apache 2.0 makes this a plausible base model for regulated industries (healthcare, finance, defense) that can't touch anything with a 'no commercial derivatives' clause, which is a genuine unlock for a market segment that's been frozen out of open-weights progress.”

“Multi-agent coding with isolated worktrees and structured pre-work phases is the right abstraction for complex software. OMX ships this today in a scrappy, hackable form that feels like a preview of where all coding agents are heading in 18 months. The project may get superseded — but the pattern it establishes won't.”

“The buyer here is the infrastructure team at a mid-market SaaS company that wants to stop paying per-token at scale — Apache 2.0 gives them a clear path to self-hosted inference with no legal surface area, which is a real budget line item. The moat question is harder: Mistral's defensible position isn't the weights (those are free), it's the brand trust in European enterprise markets and their la Plateforme API for teams who want managed inference without US hyperscaler data residency concerns. The risk is that this move commoditizes their own API business — if the weights are good enough, the managed product has to compete on latency and reliability, not model quality, and that's a thinner margin game.”

“Terminal-native and entirely engineer-focused. Zero relevance for creative workflows unless someone builds a GUI on top. Check back if a visual interface emerges.”