Pick MAI-Thinking-1 for very strong math reasoning (aime 2025 97%, aime 2026 94.5%) or microsoft's first in-house flagship reasoner, trained without openai distillation. Pick North Mini Code for agentic software engineering, code generation, and terminal tasks or efficient sparse moe — 3b active of 30b, runs on a single h100. Choose North Mini Code if you need self-hosting or data privacy; MAI-Thinking-1 if you want a managed API.
MAI-Thinking-1 (Microsoft) and North Mini Code (Cohere) are two of the models people most often weigh against each other in 2026. MAI-Thinking-1 is microsoft's first fully in-house flagship reasoning model — a Claude-class reasoner built independently to cut its OpenAI dependence. North Mini Code is cohere's first agentic coding model: an open-weight 30B/3B-active MoE built for real software-engineering and terminal tasks that runs on a single H100. Their biggest split is open vs. closed weights, and the breakdown below shows exactly how that plays out for your workload.
Key differences
Cost model: North Mini Code ships open weights you can self-host (hardware cost only, no per-token fee), while MAI-Thinking-1 is API-metered at Not published. Your choice depends on whether you want zero marginal cost at the price of running infrastructure.
Context window: both advertise 256K (~384 pages). Tie on paper — test on your own long inputs, since usable recall varies by model.
Specifications
Spec
MAI-Thinking-1
North Mini Code
Provider
Microsoft (US)
Cohere (Global)
Released
June 2, 2026
June 9, 2026
Context window
256K (~384 pages)
256K (~384 pages)
Price (in/out)
Not published
Open weight (self-host / free)
Open weight?
No — API only
Yes — self-hostable
Modalities
text, code
text, code
SWE-Bench Verified
Not published
67.6%
MRCR v2 @ 1M
Not published
Not published
Who wins what
Very strong math reasoning (AIME 2025 97%, AIME 2026 94.5%): MAI-Thinking-1 — A core design strength of MAI-Thinking-1.
Microsoft's first in-house flagship reasoner, trained without OpenAI distillation: MAI-Thinking-1 — A core design strength of MAI-Thinking-1.
Efficient reasoning at low token cost for its class: MAI-Thinking-1 — A core design strength of MAI-Thinking-1.
Agentic software engineering, code generation, and terminal tasks: North Mini Code — A core design strength of North Mini Code.
Efficient sparse MoE — 3B active of 30B, runs on a single H100: North Mini Code — A core design strength of North Mini Code.
High throughput (up to 2.8x Devstral Small 2) at low latency: North Mini Code — A core design strength of North Mini Code.
Which should you pick?
A team with data-privacy or self-hosting needs: North Mini Code — Open weights let you run it on your own hardware; MAI-Thinking-1 is API-only.
Anyone whose priority is very strong math reasoning (aime 2025 97%, aime 2026 94.5%): MAI-Thinking-1 — It is specifically built for that.
Anyone whose priority is agentic software engineering, code generation, and terminal tasks: North Mini Code — That is its strongest area.
MAI-Thinking-1: where it fits
Microsoft's first fully in-house flagship reasoning model — a Claude-class reasoner built independently to cut its OpenAI dependence. Released June 2, 2026 by Microsoft, it is built for very strong math reasoning (AIME 2025 97%, AIME 2026 94.5%), microsoft's first in-house flagship reasoner, trained without OpenAI distillation, efficient reasoning at low token cost for its class, and competitive with Claude Opus 4.6 on SWE-Bench Pro (vendor-reported).
Its trade-offs are real: closed and in private preview — no open weights, no published pricing, thin availability, and benchmarks are largely self-reported.
North Mini Code: where it fits
Cohere's first agentic coding model: an open-weight 30B/3B-active MoE built for real software-engineering and terminal tasks that runs on a single H100. Released June 9, 2026 by Cohere, it is built for agentic software engineering, code generation, and terminal tasks, efficient sparse MoE — 3B active of 30B, runs on a single H100, high throughput (up to 2.8x Devstral Small 2) at low latency, and fully open weights under Apache 2.0 with fp8 and 4-bit builds.
Its trade-offs: text-only and coding-specialized — not multimodal or general-purpose, and 256K context and modest general-intelligence index trail frontier models. As an open-weight model, its running cost is your own hardware rather than a per-token fee.
The bottom line for this matchup
The defining split here is open vs. closed. North Mini Code gives you weights you control — self-host it, fine-tune it, keep data in-house, pay only for hardware. MAI-Thinking-1 gives you a managed, always-updated API with no infrastructure to run. Teams with GPUs, privacy requirements, or huge volume often favour the open model; teams that want zero ops and the latest capabilities favour the closed one. Capability is close enough that this operational question, not the benchmark, usually decides it.
Frequently asked questions
Is MAI-Thinking-1 or North Mini Code better for coding?
Public SWE-Bench figures are not available for MAI-Thinking-1, so the honest test is your own repository — run an identical real bug through both. By design, MAI-Thinking-1 leans toward very strong math reasoning (aime 2025 97%, aime 2026 94.5%) while North Mini Code leans toward agentic software engineering, code generation, and terminal tasks, and that positioning usually predicts which feels better on your codebase.
Which is cheaper, MAI-Thinking-1 or North Mini Code?
North Mini Code is open-weight, so self-hosting means no per-token fee (you pay for hardware instead), while MAI-Thinking-1 is API-metered at Not published. For most teams without GPUs, the API model is cheaper to start; at very high volume, self-hosting can win.
Which has the bigger context window?
Both advertise 256K (~384 pages). Remember advertised ≠ usable: recall typically degrades before the ceiling.
Can I use both MAI-Thinking-1 and North Mini Code together?
Yes — a multi-model platform like LumiChats gives you MAI-Thinking-1, North Mini Code and 40+ others under one ₹69/day pass (about $1/day), so you can draft with one and cross-check with the other instead of buying two subscriptions.
Which is newer, MAI-Thinking-1 or North Mini Code?
North Mini Code — released June 9, 2026, about 7 days after MAI-Thinking-1.
MAI-Thinking-1 vs North Mini Code
Microsoft · US | Cohere · Global · Updated June 2026
Quick verdict
Pick MAI-Thinking-1 for very strong math reasoning (aime 2025 97%, aime 2026 94.5%) or microsoft's first in-house flagship reasoner, trained without openai distillation. Pick North Mini Code for agentic software engineering, code generation, and terminal tasks or efficient sparse moe — 3b active of 30b, runs on a single h100. Choose North Mini Code if you need self-hosting or data privacy; MAI-Thinking-1 if you want a managed API.
MAI-Thinking-1 (Microsoft) and North Mini Code (Cohere) are two of the models people most often weigh against each other in 2026. MAI-Thinking-1 is microsoft's first fully in-house flagship reasoning model — a Claude-class reasoner built independently to cut its OpenAI dependence. North Mini Code is cohere's first agentic coding model: an open-weight 30B/3B-active MoE built for real software-engineering and terminal tasks that runs on a single H100. Their biggest split is open vs. closed weights, and the breakdown below shows exactly how that plays out for your workload.
Key differences at a glance
▸Cost model: North Mini Code ships open weights you can self-host (hardware cost only, no per-token fee), while MAI-Thinking-1 is API-metered at Not published. Your choice depends on whether you want zero marginal cost at the price of running infrastructure.
▸Context window: both advertise 256K (~384 pages). Tie on paper — test on your own long inputs, since usable recall varies by model.
Side-by-side specs
Spec
MAI-Thinking-1
North Mini Code
Provider
Microsoft (US)
Cohere (Global)
Released
June 2, 2026
June 9, 2026
Context window
256K (~384 pages)
256K (~384 pages)
Price (in/out)
Not published
Open weight (self-host / free)
Open weight?
No — API only
Yes — self-hostable
Modalities
text, code
text, code
SWE-Bench Verified
Not published
67.6%
MRCR v2 @ 1M
Not published
Not published
Who wins what
Very strong math reasoning (AIME 2025 97%, AIME 2026 94.5%)
MAI-Thinking-1
A core design strength of MAI-Thinking-1.
Microsoft's first in-house flagship reasoner, trained without OpenAI distillation
MAI-Thinking-1
A core design strength of MAI-Thinking-1.
Efficient reasoning at low token cost for its class
MAI-Thinking-1
A core design strength of MAI-Thinking-1.
Agentic software engineering, code generation, and terminal tasks
North Mini Code
A core design strength of North Mini Code.
Efficient sparse MoE — 3B active of 30B, runs on a single H100
North Mini Code
A core design strength of North Mini Code.
High throughput (up to 2.8x Devstral Small 2) at low latency
North Mini Code
A core design strength of North Mini Code.
Which should you pick?
A team with data-privacy or self-hosting needs
→ North Mini Code
Open weights let you run it on your own hardware; MAI-Thinking-1 is API-only.
Anyone whose priority is very strong math reasoning (aime 2025 97%, aime 2026 94.5%)
→ MAI-Thinking-1
It is specifically built for that.
Anyone whose priority is agentic software engineering, code generation, and terminal tasks
→ North Mini Code
That is its strongest area.
MAI-Thinking-1: where it fits
Microsoft's first fully in-house flagship reasoning model — a Claude-class reasoner built independently to cut its OpenAI dependence. Released June 2, 2026 by Microsoft, it is built for very strong math reasoning (AIME 2025 97%, AIME 2026 94.5%), microsoft's first in-house flagship reasoner, trained without OpenAI distillation, efficient reasoning at low token cost for its class, and competitive with Claude Opus 4.6 on SWE-Bench Pro (vendor-reported).
Its trade-offs are real: closed and in private preview — no open weights, no published pricing, thin availability, and benchmarks are largely self-reported.
North Mini Code: where it fits
Cohere's first agentic coding model: an open-weight 30B/3B-active MoE built for real software-engineering and terminal tasks that runs on a single H100. Released June 9, 2026 by Cohere, it is built for agentic software engineering, code generation, and terminal tasks, efficient sparse MoE — 3B active of 30B, runs on a single H100, high throughput (up to 2.8x Devstral Small 2) at low latency, and fully open weights under Apache 2.0 with fp8 and 4-bit builds.
Its trade-offs: text-only and coding-specialized — not multimodal or general-purpose, and 256K context and modest general-intelligence index trail frontier models. As an open-weight model, its running cost is your own hardware rather than a per-token fee.
The bottom line for this matchup
The defining split here is open vs. closed. North Mini Code gives you weights you control — self-host it, fine-tune it, keep data in-house, pay only for hardware. MAI-Thinking-1 gives you a managed, always-updated API with no infrastructure to run. Teams with GPUs, privacy requirements, or huge volume often favour the open model; teams that want zero ops and the latest capabilities favour the closed one. Capability is close enough that this operational question, not the benchmark, usually decides it.
Want both MAI-Thinking-1 and North Mini Code without two subscriptions? LumiChats gives you these plus 40+ models under one ₹69/day pass (about $1/day) — draft with one, cross-check with the other.
Is MAI-Thinking-1 or North Mini Code better for coding?
Public SWE-Bench figures are not available for MAI-Thinking-1, so the honest test is your own repository — run an identical real bug through both. By design, MAI-Thinking-1 leans toward very strong math reasoning (aime 2025 97%, aime 2026 94.5%) while North Mini Code leans toward agentic software engineering, code generation, and terminal tasks, and that positioning usually predicts which feels better on your codebase.
Which is cheaper, MAI-Thinking-1 or North Mini Code?
North Mini Code is open-weight, so self-hosting means no per-token fee (you pay for hardware instead), while MAI-Thinking-1 is API-metered at Not published. For most teams without GPUs, the API model is cheaper to start; at very high volume, self-hosting can win.
Which has the bigger context window?
Both advertise 256K (~384 pages). Remember advertised ≠ usable: recall typically degrades before the ceiling.
Can I use both MAI-Thinking-1 and North Mini Code together?
Yes — a multi-model platform like LumiChats gives you MAI-Thinking-1, North Mini Code and 40+ others under one ₹69/day pass (about $1/day), so you can draft with one and cross-check with the other instead of buying two subscriptions.
Which is newer, MAI-Thinking-1 or North Mini Code?
North Mini Code — released June 9, 2026, about 7 days after MAI-Thinking-1.
Specifications and benchmarks reflect publicly reported figures as of June 2026 and may change as providers release updates. Always verify on your own workload.