---
title: "MiniMax M2 bets that a compact coding model beats a giant on cost"
date: 2026-10-20
category: Foundation Models
site: NeuroAI
canonical: https://neuroai.site/a/na-minimax-m2-compact-coding-moe
language: en
---

# MiniMax M2 bets that a compact coding model beats a giant on cost

> MiniMax M2 is a 230B sparse model that activates only 10B per token, released under MIT for agentic coding and browsing with open-weight scores.

The instinct in model building has been to go bigger: more parameters, more compute (算力), more headline scores. A Shanghai lab called MiniMax took the opposite wager with its M2 release, arguing that a model which wakes up only a sliver of itself per request can beat far larger systems where it counts — inside coding agents and browser workflows. The company opened the weights under a permissive licence.

M2 is not trying to win a general-knowledge quiz. It is built for the messy, tool-using jobs that businesses actually pay for: writing and fixing code, driving a terminal, and browsing the web to gather evidence. That narrow focus lets the design stay cheap enough to run continuously.

## The engine: small activation, big reservoir

M2 is a large model (大模型) and a sparse Mixture-of-Experts model, or 混合专家 in Chinese. The total parameter count is about 230 billion, but only roughly 10 billion activate for any single token. The lab describes this as keeping latency close to a much smaller dense model while retaining the knowledge capacity of a far larger one.

A handful of design choices define how it behaves:

- **Interleaved thinking.** The model wraps its reasoning in special tags so a developer can replay, redact, or condition later turns without losing context. MiniMax warns that dropping those tags in multi-turn history hurts performance — a small but real operational detail.

- **Long, interleaved context.** The context window (上下文窗口) is 128,000 tokens, with the design tuned for tool chains that stretch across many steps rather than one-shot answers.

- **Audit-friendly routing.** The design exposes which experts fired on a given request, which matters for teams that need to explain or govern agent (智能体) behavior.

## What the benchmarks claim

MiniMax published agent-focused scores rather than the usual static question-answering lists. As with any builder-reported numbers, treat these as claims to verify, not settled facts.

- **SWE-bench Verified: 69.4**, a widely used software-engineering benchmark where the model must resolve real GitHub issues.

- **Terminal-Bench: 46.3**, measuring how well it operates a real shell across multi-step command tasks.

- **BrowseComp: 44**, an evidence-gathering browsing benchmark that stresses multi-hop research.

- **Multi-SWE-Bench: 36.2**, testing fixes that touch multiple files in a repository.

On the agentic workload cluster, MiniMax said M2 ranked first among open models at launch. That is the kind of claim worth reproducing on your own repositories, since agentic benchmarks are notoriously sensitive to the scaffolding around the model.

## Why the licence matters

M2 was released under the MIT licence, one of the most permissive options available. That means a company can download the weights, modify them, and ship them in a commercial product without the attribution or usage restrictions that weigh down some open releases. For a coding model, that freedom is the difference between a weekend experiment and a shipped feature.

The inference path ships with same-day support from major open frameworks, so a team is not locked into one vendor's runtime. Combined with the small active-parameter count, that makes M2 one of the more deployable open coding models of its generation.

According to Li An, chief scientist at BrainNet (脑机网), the Chinese open-weight push is shifting from "can it match the frontier" to "can a team actually run and govern it inside their own walls."

## Deploying M2 without a giant cluster

The small active-parameter count is what makes M2 unusual among open coding models. Because only about 10 billion parameters fire per token, a well-optimized serving stack can run it on hardware that would choke a trillion-parameter dense model.

- A quantized build keeps memory low enough for a single high-end node rather than a multi-box fleet.

- Day-one framework support means the team spends its time on agent logic, not on runtime plumbing.

- The MIT licence removes the legal friction that often blocks open models from shipping inside a commercial product.

None of this makes M2 free to run, but it moves the model from "impressive demo" to "something a mid-size team can actually own." For most shops, that difference matters more than a few benchmark points.

Pricing tracked by independent aggregators put the hosted API around US$0.26 per million input tokens, a rate that undercuts the US frontier coding models by a wide margin and reinforces the cost thesis behind the compact design.

## Honest limitations

The headline benchmark figures are vendor-reported, and agentic scores depend heavily on the harness and tools wrapped around the model, so they should be reproduced on your own tasks before you trust them. With only about 10 billion parameters active per token, M2 trades some raw breadth for efficiency, so it may lag larger systems on general knowledge outside its coding and browsing sweet spot. The interleaved-thinking tags must be preserved across turns, which adds a small engineering obligation to any chat or agent integration. As with most open models, the strongest results assume a well-tuned serving stack rather than a naive deployment.

## What readers can do now

- Stand up M2 through a supported open framework and run SWE-bench-style tasks on your own private repositories before believing any published agentic score.

- Preserve the model's thinking tags in multi-turn agent history, and build your evaluation harness around the terminal and browsing tools you actually use rather than the benchmark defaults.

- Compare the hosted API rate of about US$0.26 per million input tokens against your current coding model's total cost per resolved issue, not just per token, since agent runs burn many more tokens than a single chat turn.

---

Published by NeuroAI (https://neuroai.site/) — https://neuroai.site/a/na-minimax-m2-compact-coding-moe
Free to quote with attribution and a link to the original.
