Inkling-Small outperforms Inkling on three of the most demanding public benchmarks, but trails on factual recall and competition math .
| Benchmark | Inkling-Small | Inkling | Delta |
|---|---|---|---|
| HLE (text-only) | 31.6% | 29.7% | +1.9 pp |
| SWE-Bench Verified | 80.2% | 77.6% | +2.6 pp |
| GPQA Diamond | 89.5% | 87.2% | +2.3 pp |
| AA Index v4.1 | 40 | 41 | –1 point |
| AIME 2026 | 95.5% | 97.1% | –1.6 pp |
| SimpleQA Verified | 20.6% | 43.9% | –23.3 pp |
Key takeaways:
Inkling-Small is a 42-layer sparse MoE transformer with 6 out of 256 experts activated per token, plus 2 shared experts . The model uses hybrid attention (a mix of full and sliding-window attention) and supports controllable thinking effort, letting developers trade latency for reasoning depth
.
The architecture is the same MoE family as Inkling but with fewer total experts (256 vs. Inkling's roughly 576) and fewer active experts per layer. The result is a model that behaves like a 12B-parameter dense model at inference time but retains the capacity of a 276B model in its weights .
Thinking Machines used a two-stage recipe that is now being studied as a standard post-training primitive in the industry :
On-policy distillation from Inkling — An earlier checkpoint (Inkling-Small preview) was trained using Inkling as the teacher. The student sampled its own trajectories while the teacher provided dense token-level supervision — a method known as on-policy distillation (OPD) . This technique combines the sample efficiency of distillation with the distributional realism of on-policy training.
Two additional weeks of agent-focused reinforcement learning — The team continued scaling agentic coding RL, which pushed the model past Inkling on reasoning and coding benchmarks .
This recipe is notable because the student surpassed its teacher on several tasks after only two weeks of additional RL — a result that aligns with recent research on weak-to-strong generalization via on-policy distillation .
Inkling-Small drastically lowers the hardware bar for open-weight models. Below are the official configurations from the model card :
| Format | Aggregated VRAM | Example Configurations |
|---|---|---|
| BF16 | ~600 GB | 4× NVIDIA B300 or 8× H200 |
| NVFP4 (W4A16) | ~180 GB | 2× NVIDIA H200 |
| NVFP4 (W4A4) | ~180 GB | 1× NVIDIA B300 (requires SM100+) |
For context, Inkling's BF16 checkpoint required ~1.9 TB of aggregated VRAM . The official NVFP4 quantized variant of Inkling required ~600 GB
.
This 3x VRAM reduction makes Inkling-Small the first model in the Thinking Machines lineup that is realistically accessible for LoRA and full-parameter fine-tuning by mid-sized teams without massive multi-node clusters . The model supports BF16, MXFP8, and NVFP4 numerics
.
Thinking Machines Lab was founded by former OpenAI CTO Mira Murati after she left OpenAI in 2024. John Schulman (former OpenAI co-founder of the RLHF team) is also a co-founder. Lilian Weng — who was initially part of the founding team — has since departed Thinking Machines Lab and returned to OpenAI. This leaves Mira Murati and John Schulman as the remaining co-founders of the startup .
Inkling-Small is a strong statement from Thinking Machines Lab: with the right post-training recipe, a model one-quarter the size can not only match but exceed its larger teacher on reasoning and agentic coding tasks. For developers and organizations that were priced out of running Inkling (1.9 TB VRAM), Inkling-Small opens the door at 600 GB (BF16) or even 180 GB (NVFP4). The trade-off is a significant hit to factual recall, but for coding, reasoning, and instruction-following workloads, Inkling-Small is the more practical open-weight choice as of July 2026.