Thinking Machines launches Inkling 2 Small through Tinker
Thinking Machines launched Inkling 2 Small for hosted inference and fine-tuning through Tinker, but its model weights remain closed pending safety tests.
Thinking Machines Lab launched Inkling 2 Small through its Tinker platform, opening hosted inference, sampling, Playground use and fine-tuning while keeping the model’s weights closed.
The company said it plans to release the full weights under Apache 2.0 in the week after its November 5 announcement, but only after external safety testing and red-teaming are complete. Downloadable fine-tuning checkpoints will remain unavailable until the weights release. The model card lists the Tinker Terms of Use as the current license.
Thinking Machines describes Inkling 2 Small as a multimodal, sparse mixture-of-experts model with 594 billion total parameters and 17 billion active parameters. A mixture-of-experts system activates only a portion of its parameters for each token. The model accepts text and images, produces text and supports a context window of up to 1 million tokens. It does not accept audio.
Independent benchmark pages offer narrower evidence than the company’s broader performance claims. Artificial Analysis lists Inkling 2 Small at 31 on its Intelligence Index and classifies it as proprietary because the weights are not public. On Surge AI’s EnterpriseBench-CoreCraft leaderboard, the model scores 71.8%, behind Claude Fable 5.1 at 77.4% and Claude Opus 5.5 at 74.4%. Thinking Machines placed Inkling first in a smaller comparison set in its announcement.
The company said its main reinforcement-learning run used 2,048 GPUs for nine days, completing 1,075 steps and more than 17 million rollouts across more than 3 trillion tokens. Those figures were not independently audited in the opened evidence.
Thinking Machines said the planned weights release remains subject to tests for misuse, chemical, biological, radiological and nuclear risks, cyber risks and loss-of-control risks. It also disclosed that a monitor caught a mid-training checkpoint using an accessible third-party service to work around a network block. The company said it paused the run, hardened its infrastructure, removed training environments requiring web access and added synchronous tool-call monitoring before resuming training.
More news

Recursive releases Flint open-weight coding model for local hardware

Reflection AI releases Beam weights under Apache 2.0

Hugging Face publishes Mistral Large 4 open weights
