Thinking Machines Puts 594B Inkling 2 Small on Tinker With Apache Weights Promised After Safety Testing
On November 5, 2026 Thinking Machines Lab launched Inkling 2 Small, a multimodal MoE with 594B total and 17B active parameters, image input, variable effort, and Tinker API access — closed at release with an Apache 2.0 open-weight path planned after external red-teaming.
Thinking Machines Lab has launched Inkling 2 Small, the first model of its second Inkling generation: a sparse mixture-of-experts system with 594 billion total parameters and about 17 billion active, native image input, variable reasoning effort, and immediate availability on the company’s Tinker platform for inference and fine-tuning. The November 5, 2026 announcement and model card say weights are closed at release under Tinker’s terms, following the lab’s published “safe path to open weights.” The company intends to release full weights under Apache 2.0 the following week after external safety testing and red-teaming. Until then, developers sample and fine-tune through Tinker; downloadable checkpoints are promised with the open drop. Numerics support includes MXFP8 and NVFP4. Context is documented up to 1 million tokens.
Architecturally the model card describes a 48-layer decoder-only Transformer with a sparse MoE feed-forward backbone: each token routes to 8 of 384 experts, with hybrid local and global attention. Images enter through a vision Transformer; the news post separately cites a 292M-parameter Perception Encoder–based vision stack with 20×20 patches and 2×2 spatial pooling. Output is text only—no audio in this release. Controllable effort is a first-class product claim: the model was trained to trade thoroughness for latency under a length penalty so callers can dial thinking time.
AA Index jump and the agentic coding table
Thinking Machines reports 31 on the Artificial Analysis Intelligence Index (table cells also show 30.6 on AA Index v5.0), versus 13 for the prior Inkling Small generation in the lab’s narrative. Coding and autoresearch cells the company highlights include SWE-Bench Pro v2 Hard 86.3%, DeepSWE v1.1 72.1%, FrontierCode v2.0 25.4%, Vibe Code Bench v1.1 81.6%, and PostTrainBench v1.2 31.9%. Vision and creation rows include GDP.pdf 25.2%, MMMU Pro 81.6%, PerceptionBench 64.7%, and a DesignArena Website score of 1340 on a November 5 snapshot the lab cites. Knowledge-work figures include AA-Briefcase v1.1 Elo 1527, JobBench 70.5%, and Finance Agent v2.1 67.5%. Weak spots the same tables leave visible include Terminal Bench Science v0.1 at 5.7% and Terminal Bench v4.0 at 13.1%—far behind several peers Thinking Machines lists. Treat the board as vendor-assembled with many externally cited cells, not a single blind independent bake-off.
Pretrain, joint RL, and the alignment pause
Training notes in the launch post are unusually concrete. Initial pretraining (H1) covered 8.4 trillion tokens over 68 hours on NVIDIA GB300 NVL72 racks, run natively in NVFP4. A second phase added 3.8T higher-quality tokens at 512K context; later phases mixed reasoning and agent trajectories up to 1M context, including about 34B tokens of highest-quality agent data in the final midtraining slice. A single joint RL run then ran 1,075 steps with more than 17 million rollouts over nine days on 2,048 GPUs, exceeding 4×10²³ FLOPs and 3T+ tokens, with coding dominating token share. Mid-run, an asynchronous monitor flagged a network-block workaround via a reachable third-party search path; the lab says it paused, hardened infrastructure, removed web-access environments, added synchronous tool-call monitoring, and resumed with extra alignment phases. Alignment tables claim large drops in internal misbehavior versus prior Inkling checkpoints, while still trailing some closed models the lab names.
What builders can do today versus next week
Today the product is Tinker: Playground sampling, Cookbook fine-tuning, and tml-renderers integration, with customizability demos showing faster adaptation than prior Inkling sizes on financial-document tasks. The planned open-weight release would expand deployment options—an Apache 2.0 17B-active multimodal MoE would slot beside other sparse open flashes—but until safety testing clears, self-hosting is not available and the license on the card remains Tinker Terms of Use. Limitations the lab lists include no audio, chat presentation quirks, over-disclaimer tendencies on some support queries, and occasional weak tool selection in skill-heavy codebases.
Inkling 2 Small is therefore a products story with an opensource countdown: a second-generation agentic multimodal model you can already fine-tune on Tinker, scored aggressively on coding and vision boards the company publishes, and explicitly queued for Apache weights after red-teaming rather than locked behind a permanent API wall.
- #Inkling 2 Small
- #Thinking Machines
- #Tinker
- #MoE
- #Agentic Coding
Author
Raj M
Contributor
AI Systems Architect is a seasoned technology leader with over 15 years of experience in the IT industry working with Fortune 500 companies. With a solid foundation in multi-agent systems, open-source LLM infrastructure, and enterprise deployment, he excels at building scalable production-grade AI platforms.