Luxsynthesis Blog
All articles
Models

Thinking Machines Releases Inkling: A 975B Open-Weight Multimodal Foundation Model

Thinking Machines has released Inkling, an open-weight model trained from scratch: a 975B-total / 41B-active MoE multimodal foundation model with native text, image, and audio input, up to 1M-token context, and controllable thinking effort. Full weights are on Hugging Face, and a 12B-active Inkling-Small was previewed alongside.

Author
Luxsynthesis
Published
Reading time
10 min read
Thinking Machines Releases Inkling: A 975B Open-Weight Multimodal Foundation Model

Thinking Machines has released Inkling, an open-weight model trained from scratch, with full weights published simultaneously. The company positions it as a "customizable multimodal foundation model" rather than a model chasing top spot on any single benchmark.

Alongside Inkling, the team also previewed the lighter Inkling-Small (12B active parameters), the first small-size variant in the family.

Core Specs

Inkling family core specs

Two sizes of the same MoE architecture. Donuts show active params per token as a share of total params.

InklingFull weights released
41Bactive
Active / token41B
Total975B

~4.2% active per token

Architecture
MoE Transformer
Context
up to 1M tokens
Pretraining
45T tokens (text / image / audio / video)
Weights
Hugging Face, incl. NVFP4 checkpoint
Inkling-SmallPreview · weights after testing
12Bactive
Active / token12B
Total276B

~4.3% active per token

Architecture
MoE Transformer
Context
not disclosed
Pretraining
similar recipe, data & recipe optimized
Weights
after testing completes

Core Capabilities

Inkling's emphasis is not on being the strongest on any single dimension, but on breadth and customizability. The team trained it across agentic tasks, reasoning, coding, instruction following, factuality, vision, and audio, aiming to make it a foundation model that can be fine-tuned into a variety of workflows. Per-dimension benchmark data is detailed in the "Benchmark Performance" section below.

Agentic Coding and Tool Use

Inkling is designed to run across multiple coding / agent harnesses. During training, the tool sets and schemas were randomized to reduce sensitivity to any specific harness. The team showcased several categories of demos:

  • Single-pass web app generation: generated a job-application web page from a prompt, then invoked a browser agent to auto-fill the form using a saved resume.
  • Design Arena: on a blind human-evaluation Agentic Web Dev leaderboard, Inkling ranks among the top open-weight models.
  • Consistent multi-page documents: generated a 9-page PDF food-and-travel journal from a prompt.
  • Long-iteration game optimization: with GPT Codex acting as reviewer, Inkling produced a multiplayer online Snake game over 40 rounds of feedback iteration.

Controllable Thinking Effort

Inkling supports tuning an effort parameter to balance performance against token consumption. The team ran an effort sweep (effort from 0.2 to 0.99) on Terminal Bench 2.1, HLE (Humanity's Last Exam), and IFBench. The overall trend: Inkling generates fewer tokens to reach an equivalent score. For example, on Terminal Bench 2.1, Inkling reaches the same score as Nemotron 3 Ultra using roughly one-third the tokens.

Controllable thinking effort: performance vs. token cost (schematic)

Drag the effort parameter to see how the two move relative to each other. Curves are schematic, not official per-point data.

effort0.85
0.20.99
Relative score (schematic)95%
Token consumption (schematic)72%

The official effort sweep (0.2 → 0.99 on Terminal Bench 2.1 / HLE / IFBench) shows rising returns with effort, while token cost grows faster; Inkling needs fewer tokens to reach an equivalent score.

Terminal Bench 2.1: tokens needed to match Nemotron 3 Ultra's score (official figure)
Nemotron 3 Ultra100%
Inkling≈33%

Multimodal Capabilities

Inkling natively supports text, image, and audio input. The vision and audio components use an encoder-free architecture: audio uses dMel spectrograms, images are tiled into 40×40 pixel patches, and both pass through a lightweight embedding layer before being processed jointly with text tokens.

The multimodal benchmark comparisons provided by the team are as follows (all at effort=0.99):

Multimodal benchmark radar (effort=0.99)

Switch between vision and audio; click a legend item to hide a model, hover a vertex for values.

MMMU ProCharxiv RQCharxiv RQ + Py

Epistemics

Thinking Machines groups calibration, instruction following, and censorship resistance under the collective term "epistemics."

  • Calibration: Inkling's results on ForecastBench and Prophet Arena fall in the same range as models like GPT-5.5 and Gemini 3.1 Pro.
Calibration (ForecastBench / Prophet Arena)

Colors are normalized within each row; Prophet Arena is a Brier score where lower is better (color direction inverted); ± ranges omitted.

Inkling
GPT-5.5
Claude Opus 4.8
Gemini 3.1 Pro
Grok 4.3
Kimi K2.6
ForecastBench · no search
61.1
59.1
54.6
61.1
61.7
58.1
ForecastBench · with search
63.7
64.7
58.6
64.3
63.2
Prophet Arena Brierlower is better
0.1617
0.1598
0.1605
0.1594
0.1715
0.1675
Weaker (within row)Strongest (within row)
  • Instruction following and factuality: post-training used two automated graders — a rubric grader and a claims grader. The latter invokes search to verify factual claims, reducing hallucination.
  • Censorship resistance: on Cognition's Propaganda and Censorship Eval, Inkling exhibited strong censorship-resistant behavior.

Safety

Safety comparison

Colors are normalized within each row. FORTRESS (Adversarial) measures harmful-request refusal; (Benign) measures low over-refusal.

Inkling
Nemotron 3 Ultra
Kimi K2.5
Kimi K2.6
GLM 5.2
DeepSeek V4 Pro
FORTRESS (Adversarial)
78.0
77.6
54.1
65.6
71.3
36.0
FORTRESS (Benign)
95.9
90.5
98.3
97.2
90.0
98.5
StrongREJECT
98.6
98.7
99.5
99.8
98.5
98.6
Weaker (within row)Strongest (within row)

The team states that Inkling has a high refusal rate for harmful requests on FORTRESS while maintaining a low false-refusal rate for benign requests.

Benchmark Performance

All scores below were measured at effort=0.99, temperature=1.0; coding evaluations used a max-token trajectory limit of 256K.

Benchmark heatmap (effort=0.99, temperature=1.0)

Colors are normalized within each row so different scales stay comparable; coding evals used a 256K max-token trajectory.

Inkling
Nemotron 3 Ultra
Kimi K2.5
Kimi K2.6
GLM 5.2
DeepSeek V4 Pro
Gemini 3.1 Pro
Claude Fable 5
GPT 5.6 Sol
HLE text only
29.7
26.6
29.4
35.9
40.1
35.9
44.7
53.3
47.2
HLE with tools
46.0
37.4
50.2
54.0
54.7
48.2
51.4
64.5
55.0
AIME 2026
97.1
94.2
95.8
96.4
99.2
96.7
98.3
99.9
99.9
GPQA Diamond
87.2
86.7
87.9
91.1
89.5
88.8
94.1
92.6
94.1
Weaker (within row)Strongest (within row)

Inkling's remaining scores

Inkling scores on factuality, instruction following, vision, audio, and safety (effort=0.99)

Values are percentages. SimpleQA Verified comparison: DeepSeek V4 Pro 57.0%, Gemini 3.1 Pro 77.3%, Claude Fable 5 68.3%, GPT 5.6 Sol 71.6%. AA Omniscience scored 2.1 (not a percentage; omitted from the chart).

020406080100StrongREJECT (safety)StrongREJECT …FORTRESS Benign (safety)FORTRESS Beni…VoiceBench (audio)VoiceBench (a…Global-MMLU-LiteGlobal-MMLU-L…Charxiv RQ + Python (vision)Charxiv RQ + …IFBench (instruction)IFBench (inst…Charxiv RQ (vision)Charxiv RQ (v…FORTRESS Adversarial (safety)FORTRESS Adve…MMAU (audio)MMAU (audio)MMMU Pro (vision)MMMU Pro (vis…Audio MC (audio)Audio MC (aud…SimpleQA Verified (factuality)SimpleQA Veri…
未选择数据
  • StrongREJECT (safety):98.6
  • FORTRESS Benign (safety):95.9
  • VoiceBench (audio):91.4
  • Global-MMLU-Lite:88.7
  • Charxiv RQ + Python (vision):82
  • IFBench (instruction):79.8
  • Charxiv RQ (vision):78.1
  • FORTRESS Adversarial (safety):78
  • MMAU (audio):77.2
  • MMMU Pro (vision):73.5
  • Audio MC (audio):56.6
  • SimpleQA Verified (factuality):43.9

Training and Architecture

Architecture

Inkling's MoE design draws primarily from DeepSeek-V3:

  • 256 routed experts + 2 shared experts per layer; 6 routed experts activated per token
  • Sigmoid-based router + auxiliary-loss-free load-balancing bias
  • Attention: sliding-window layers interleaved with global layers at a 5:1 ratio; 8 KV heads
  • Uses relative positional embeddings rather than RoPE
  • Short convolutions added after the attention key/value projections and before the residual branch output
MoE routing: each token activates only a few experts

Highlighted cells are the routed experts active for the current token; a new batch lights up every ~2s to simulate incoming tokens.

Token
Router (sigmoid + balancing bias)
2 shared experts (always active)
Weighted-sum output
Total params975B
Active params / token41B

~4.2% active per token.

  • routed expert (active)
  • routed expert (idle)
  • shared expert (always on)

Per Inkling's official disclosure: 256 routed + 2 shared experts per layer, with 6 routed experts activated per token.

Training

  • Pretraining: 45 trillion tokens, covering text, image, audio, and video
  • Optimizer: Muon for large-matrix weights, Adam for all other parameters
  • Learning rate and weight decay coupling: weight decay magnitude is tied to the square of the learning rate, keeping weight scale stable
  • Post-training: covers math, agentic code and tool use, audio, image, conversation, safety, and other domains
  • Post-training starts with synthetic-data SFT (including data generated with Kimi K2.5), followed by large-scale RL

Large-Scale RL

Inkling's post-training relies on large-scale asynchronous RL, accumulating over 30 million rollouts. The aggregate eval reward reported by the team rises from 0.264 at SFT initialization to 0.356 at the release checkpoint (~26.5 million rollouts); on aggregate metrics across reasoning benchmarks (AIME, HLE, GPQA), reward improves log-linearly with rollout count.

Inkling-Small

Inkling-Small is the lightweight preview of the same model family: 276B total parameters, 12B active. Thanks to optimized pretraining data and recipe, it approaches or matches Inkling on many benchmarks.

Inkling vs. Inkling-Small: parity across 21 benchmarks

Each dot is a benchmark: x = Inkling, y = Inkling-Small. Above the diagonal means Small wins; below means Inkling leads. Hover for details.

Small ties or leadsInkling leads
00252550507575100100Inkling (effort=0.99) →Inkling-Small →

Most dots hug the diagonal — Small is close to Inkling overall; SimpleQA, Tau 3 Banking, and Terminal Bench 2.1 are the few notable laggards.

The team states that Inkling-Small is suited for cost- and latency-sensitive scenarios such as coding, LLM-as-judge scoring, and synthetic data generation. Full weights will be released after testing completes.

Customization and Availability

A key direction for Inkling is customizability:

  • Now available on the Tinker platform with fine-tuning support
  • Context length selectable at 64K or 256K
  • Limited-time 50% discount (full pricing in official docs)
  • Tinker console adds Inkling Playground with a free trial period
  • Updated cookbook with new recipes targeting Inkling's audio capabilities
  • Released tml-renderer for reliably sampling and handling tool calls, reasoning content, and multimodal input

The team also demoed Inkling self-fine-tuning: the model writes its own fine-tuning job, runs it, and evaluates the results.

Ecosystem Integration

  • API: TogetherAI, Fireworks, Modal, Databricks, Baseten
  • Inference frameworks: SGLang / Miles (RadixArk), vLLM (Inferact), TokenSpeed (Lightseek), llama.cpp (Unsloth), Hugging Face transformers
  • Weights: Hugging Face (original checkpoint + NVFP4 checkpoint, optimized for NVIDIA Blackwell)

Reference Links

All articles