Thinking Machines LabNovember 20, 2026

Inkling 2 Mini

Thinking Machines Lab’s 26.4B-total (5.4B effective active) looped MoE multimodal reasoning model with 1M context and Apache 2.0 weights.

Text + Image inputText outputOpen weights

At a glance

Context window
1M tokens
Max output
—
Text input / output · per 1M tokens
$0.150 / $0.500
Knowledge cutoff
—

Benchmark snapshot

Best result in 6 of 9 categories

View benchmark details (25)

Benchmark details

25 results · Best published score per benchmark, grouped by category

Benchmark · settingScoreRank
Academic
HLE-Diamond

Thinking (No Tools) · Knowledge Exams

15.213 / 16
Coding
DeepSWE

Thinking (With Tools) · Repository Engineering

48.261 / 73
FrontierCode 2.0

Thinking (With Tools) · Repository Engineering

15.126 / 36
Vibe Code Bench v1.1

Thinking (With Tools) · Code Generation & Editing

77.938 / 121
Computer Use
AutomationBench-AA

Thinking (With Tools) · Tool Orchestration

41.817 / 18
MCP-Atlas

Thinking (With Tools) · Tool Orchestration

82.714 / 55
ScreenSpot-Pro (no tools)

Thinking (No Tools) · GUI Grounding

76.54 / 8
General Evaluation
AA Intelligence Index v5.0.1

Thinking (No Tools) · Capability Indices

20.144 / 62
Vals Index v2.2

Thinking (With Tools) · Capability Indices

46.531 / 36
Long Context
LongBench v2

Thinking (No Tools) · Long Reasoning

66.92 / 22
OpenAI MRCR v2 (8-needle, 256K–512K)

Thinking (No Tools) · Long Retrieval

46.43 / 5
Multimodal
Chartography

Thinking (With Tools) · Documents & Charts

72.516 / 29
GDP.pdf

Thinking (No Tools) · Documents & Charts

16.838 / 96
MMMU-Pro

Thinking (No Tools) · Visual Understanding

74.969 / 136
OmniDocBench

Thinking (No Tools) · Documents & Charts

92.81 / 6
PerceptionBench

Thinking (No Tools) · Visual Understanding

57.511 / 19
ZeroBench Main

Thinking (With Tools) · Visual Understanding

34.016 / 21
Professional
AA-AnalystAgent

Thinking (With Tools) · Data Analysis

46.316 / 39
AA-Briefcase

Thinking (With Tools) · Office & Business

1263Elo18 / 20
GDPval-AA v2

Thinking (With Tools) · Cross-industry Work

1319Elo19 / 23
JobBench

Thinking (With Tools) · Cross-industry Work

49.6Unranked
Reasoning
ARC-AGI-1

Thinking (No Tools) · Abstract Generalization

84.547 / 87
ARC-AGI-2

Thinking (No Tools) · Abstract Generalization

49.345 / 80
Research & Search
BrowseComp

Thinking (With Tools) · Fact Finding

79.024 / 61
DeepSearchQA

Thinking (With Tools) · Fact Finding

85.34 / 9
15 more results in Long Context, Multimodal, Professional and 2 more

Rank is this model's position among every model with a published result on that leaderboard; the bar shows how far up the field that is. Orange marks first place on leaderboards with at least 5 models. Unranked leaderboards publish a composite or direction-less score.

Back to benchmark snapshot ↑

API pricing

Standard text rates, USD per million tokens · effective 2026-11-20

Input
$0.15
Output
$0.50
Cached input
$0.015

Blended price4:1 input:output · 90% of input tokens cached · same basis as the price ranking

$0.1228/ 1M tokens

Estimate running cost for Inkling 2 Mini

Specifications

Provider
Thinking Machines Lab
Model type
Reasoning model
Released
November 20, 2026
Total parameters
26.4B
Active parameters
5.4B
Architecture
Mixture of experts
Context window
1M tokens
Input
Text, Image
Output
Text
Licence
Apache 2.0
Commercial use
Commercial use allowed

Capabilities

ReasoningCodingTool useLong context

Model analysis

Inkling 2 Mini is Thinking Machines Lab’s compact open-weights multimodal reasoning model, released on November 20, 2026. Built on a looped sparse Mixture-of-Experts (MoE) architecture with 26.4B total parameters and 3.4B unique active parameters (5.4B effective active parameters per token across three middle-layer passes), it is designed for local workstations and edge devices. Shipped natively in mixed NVFP4 and MXFP8 precisions at roughly 20GB, it runs offline on Apple Silicon Macs with 32GB+ unified memory or a single NVIDIA DGX Spark. Full weights are available under Apache 2.0 on Hugging Face, alongside hosted inference and fine-tuning on Tinker.

A 24-layer looped MoE achieving 48 logical layer applications

Inkling 2 Mini has 24 decoder layers (128 experts per layer, 8 routed per token) organized into four 6-layer blocks: the first and last blocks run once, while the middle 12 layers (layers 6–17) loop three times with shared weights using gating and Attention Residuals, delivering 48 logical layer evaluations per token from 24 stored layers. Attention combines local and global layers. Images are encoded by a native vision transformer (40px to 4096px recommended per side) and processed jointly with text to produce text outputs; audio and video outputs are not supported.

The model supports up to a 1M-token context window (model_max_length: 1048576 in config.json) and bundles a DSpark speculative drafter to accelerate decoding. Note that TML-d24-varloop-research, released alongside it for monitorability experiments, is a separate variable-loop research checkpoint rather than an alias for Inkling 2 Mini.

Tinker API pricing and local runtime ecosystem

On Tinker, Inkling 2 Mini is offered in 64K (thinkingmachines/Inkling-2-Mini) and 256K (thinkingmachines/Inkling-2-Mini:peft:262144) training configurations, both supporting up to 1M-token sampling. Inference costs $0.15 per million input tokens, $0.015 for cached input, and $0.50 for output; fine-tuning is billed separately at $0.75 (64K) and $1.50 (256K) per million tokens. Day-zero local inference support includes vLLM, SGLang, llama.cpp (GGUF), Ollama, Unsloth, NVIDIA Dynamo, TokenSpeed, and Exo Labs.

Independent evaluation: high intelligence density with verbose reasoning

In Artificial Analysis’s independent evaluation, Inkling 2 Mini scores 20 on the AA Intelligence Index v5.0 (20.1 unrounded in the model card), reaching 280 output tokens/s with a 9.72s time to first answer token. However, its reasoning traces are verbose, generating 161M output tokens across the Intelligence Index (versus an 85.7M peer median), averaging 9.0 minutes and $0.59 per task. Separately, in Stanford’s Intelligence per Watt testing on NVIDIA DGX Spark (128GB, MXFP8, low reasoning effort), Inkling 2 Mini scored 0.703, ahead of Qwen3.6-35B-A3B (0.430), Gemma-4-26B-A4B (0.159), and Qwen3.5-27B (0.036).

Published benchmark results with harness and dual-metric conditions

The table below records the complete comparison scores from the official Hugging Face model card (thinkingmachines/Inkling-2-Mini), preserving benchmark versions, harnesses, and original/with-Python or Full/Hard pairings:

Published evaluationScore
AA Index (v5.0)20.1
Vals Index (v2.2)46.5%
FrontierCode v2.0 (stirrup v0.2.1)15.1%
DeepSWE v1.1 (mini-swe-agent v2.4.6)48.2%
Terminal Bench v4.0 (mini-swe-agent v2.4.6)5.6%
Terminal Bench v2.1 (pi v0.83.0)71.6%
SWEBench Pro v2 (Hard, mini-swe-agent v2.4.6)77.9%
SWEBench Multilingual (bash only)73.7%
SWEBench Verified (bash only)79.2%
Vibe Code Bench v1.1 (openhands / vals)77.9%
PMPP-Hard (AUC, 0–10h, pi v0.83.0)455.82
BrowseComp (with compaction)79.0%
DeepSearchQA (with compaction)85.3%
MCP Atlas (Public)82.7%
AA-Briefcase v1.11263
GDPVal-AA v2.11319
JobBench49.6%
AutomationBench-AA v1.0.641.8%
EnterpriseOps-Gym42.0%
Vals Finance Index50.1%
AA-AnalystAgent46.3%
Diligence Bench (Best harness)48.6%
GDP.pdf16.8%
PerceptionBench57.5%
MMMU Pro (Standard 10)74.9%
OmniDocBench v1.692.8%
ScreenSpot Pro (original / with Python)76.5/87.7%
Chartography (original / with Python)22.1/72.5%
ZeroBench (main, original / with Python)17.0/34.0%
MuirBench77.5%
BVB68.4%
HLE-Diamond15.2%
CritPt v2 (Full / Hard)31.4/17.0%
Apex 202534.4%
ARC-AGI (v1 / v2)84.5/49.3%
LongBench v266.9%
GraphWalks BFS (256K)69.7%
MRCR v2 (8-needle 256K–512K)46.4%
AA-Omniscience v1.1 (score)-8.6
AA-Omniscience v1.1 (non-hallucination rate)63.4%
ComplexConstraints v1.1 (openhands v1.45.0)33.4%
FORTRESS (adversarial, Public)89.5%
FORTRESS (benign, Public)96.4%
StrongREJECT (none)97.8%
Misbehavior (Internal, ↓)9.8%
Covert misbehavior (Internal, ↓)8.3%
Destructive actions (Internal, ↓)10.2%

Fit and known limitations

Inkling 2 Mini excels at local software engineering, terminal agents, document parsing (92.8% on OmniDocBench v1.6), and web-search tool use. However, the model card highlights clear boundaries: factual recall is limited by its 26.4B total parameter count (-8.6 on AA-Omniscience v1.1); debugging tasks can occasionally trigger repetitive reasoning loops (requiring token and turn limits); agentic runs should be sandboxed because it may delete or overwrite files without confirmation; non-English output (such as Chinese) can be clipped or mixed; and setting reasoning effort to minimum does not fully disable reasoning.

Sources: Official release · Hugging Face · Model card · Tinker pricing · Artificial Analysis

Last reviewed 2026-11-21

Questions

How does Inkling 2 Mini's looped architecture work?
It has 24 decoder layers (128 experts, 8 active per token) where the middle 12 layers share weights and loop three times per token, yielding 48 logical layer applications and 5.4B effective active parameters from 3.4B unique active weights.
Can Inkling 2 Mini run locally?
Yes. Distributed at roughly 20GB in mixed NVFP4 and MXFP8 precisions under Apache 2.0, it runs locally on Apple Silicon Macs with 32GB+ unified memory or a single NVIDIA DGX Spark via vLLM, SGLang, llama.cpp, or Ollama.
What is the Tinker API pricing?
Inference is priced at $0.15 per million input tokens, $0.015 for cached input, and $0.50 for output. Fine-tuning is billed separately at $0.75/1M (64K) or $1.50/1M (256K).

Editor updates

What changed for this model, noted by LLMLearner Editorial with the source it came from.

  1. Early local-AI reception praises capability per GB, flags looped-layer speed and tooling friction

    Launch-week community feedback across Hacker News, r/LocalLLaMA and r/LocalLLM is notably enthusiastic about Inkling 2 Mini's capability-to-footprint ratio, while flagging early runtime and agent-harness friction.

    What testers like. Hands-on users running the 26B looped MoE (~20 GB upstream mixed precision; ~17.6 GB in Unsloth's UD-Q4_K_XL GGUF) highlight clean prose, strong single-shot coding and 3D/spatial demos (such as Three.js mini-games), and solid localized knowledge. Several threads on r/LocalLLM compare its feel favorably against dense 27B-class models like Qwen3.8-27B, and commenters note that native NVFP4 training holds up well under 4-bit community quantization.

    Where launch-day friction shows up. Because the middle 12 layers run three times per token (48 logical layer passes), stock llama.cpp builds drew complaints over sluggish local throughput compared with optimized vLLM setups, prompting rapid patches across Vulkan backends and custom forks such as NInfer-all. Users on 24 GB cards also noted fast KV-cache growth at long context lengths.

    Agent and refusal quirks. Some CLI coding-agent testers on r/LocalLLaMA reported formatting glitches—such as dumping oversized edits into a single shell call and burning token budgets—while strict default safety refusals led to an uncensored community derivative within hours of release. As inference engines optimize looped-layer execution over the next few weeks, day-one speed complaints should be treated as transitional rather than final hardware limits.

    Hacker News launch discussion (Inkling 2 Mini)

LLMLearner on Inkling 2 Mini

Our editorial read, one angle at a time, with the evidence behind each one.

Real-world reliability

Strong capability for a 26B footprint, with early agent-formatting and refusal quirks

Early hands-on reviews from Hacker News, r/LocalLLM and r/LocalLLaMA broadly agree that Inkling 2 Mini punches above its active parameter count (~3.4B–5.4B active across looped passes). Testers praise its readable prose, localized factual recall, and single-shot coding and Three.js spatial demos, often comparing its overall feel to dense 27B-class models.

In multi-step agent loops, however, launch-week reliability is more uneven than headline SWE benchmarks imply. Developers testing it in CLI coding agents report occasional tool-call formatting issues—such as trying to push large code edits into a single bash command and exhausting token budgets—alongside verbose reasoning traces that add latency (echoing Artificial Analysis's independent note on reasoning verbosity).

Default safety guardrails are also strict enough to trigger unwanted refusals on benign edge prompts, which prompted community abliterated checkpoints on day one. Before adopting it for unattended coding workflows, test it inside your actual agent harness with explicit tool-use constraints rather than relying on one-shot demos.

MixedAI-assistedUpdated Nov 21, 2026
5 sources

Privacy and deployment

Apache 2.0 weights fit a 24 GB GPU or 32 GB Mac, but looped layers still need runtime tuning

With Apache 2.0 weights and a ~20 GB upstream mixed-precision footprint (or ~17.6 GB in Unsloth's UD-Q4_K_XL GGUF), Inkling 2 Mini hits the local-hardware sweet spot: a multimodal, 1M-context-capable model that fits on a single 24 GB consumer GPU or a 32 GB+ unified-memory Apple Silicon Mac. Because Thinking Machines Lab trained the weights natively in mixed NVFP4/MXFP8 precision, early community testers report that 4-bit GGUF quants retain quality well.

The main deployment caveat is its non-standard looped transformer architecture: 24 physical decoder layers execute 48 logical layer passes per token (the middle 12 layers loop three times). Launch-day r/LocalLLaMA testers found stock llama.cpp throughput sluggish on consumer hardware compared with vLLM on datacenter GPUs, and noted that high context lengths expand the KV cache rapidly on 24 GB cards.

Ecosystem support is moving fast—Unsloth GGUFs, Ollama, LM Studio, Vulkan backend patches and custom runtimes such as NInfer-all landed within hours—so local deployers should expect meaningful speed gains over the coming weeks rather than treating day-one llama.cpp numbers as the final ceiling.

MixedAI-assistedUpdated Nov 21, 2026
4 sources

Inkling 2 Mini vs competitors

Comparable results only · record is Inkling 2 Mini's wins–losses

Inkling 2 Mini benchmark scores against competitors
BenchmarkInkling 2 MiniThis modelvs Qwen3.8-27BRecord 14–7vs Muse Glimmer-30BRecord 19–0
MMMU-Pro74.976.374.0
GDP.pdf16.816.411.8
DeepSWE48.242.24.4
AA Intelligence Index v5.0.120.120.16.3
BrowseComp79.061.663.9
MCP-Atlas82.777.375.5
FrontierCode 2.015.114.91.5
Chartography72.552.125.1
GDPval-AA v213191427953
LongBench v266.952.333.1

Community discussion

Share the API, setup, and tradeoffs you actually tested. Rate the model once; comment as often as you like.

Used this model? Sign in with Google to rate it and share what worked, what did not, and which API or setup you tested.

No community comments yet.