Inkling shifts the open-weight question toward fine-tuning
Original: Inkling: Our Open-Weights Model View original →
Thinking Machines Lab’s first open-weights model, Inkling, landed on Hacker News because it sits at an interesting point in the model market. The company is not framing it as the strongest model overall. It is presenting a base that developers can inspect, run, and adapt: multimodal, Mixture-of-Experts, equipped with controllable reasoning effort, and available for fine-tuning through Tinker.
That positioning matters more than a single benchmark table. Inkling is described as a model for customization, including audio capability and long-context use cases that are hard to judge from aggregate scores alone. The open-weights release gives the community a path to local experimentation, while Tinker gives Thinking Machines a managed workflow for teams that want to tune the model without building every training and evaluation tool themselves.
The HN discussion quickly moved in that direction. Several commenters treated Inkling as a possible American counterpart to the increasingly strong Chinese open models from labs such as DeepSeek, Moonshot, and Z.ai. Others were more practical: they wanted GGUF builds, llama.cpp paths, private evals, audio tests, and harness-level behavior before drawing conclusions. That is the normal rhythm for an open model release. The public evals start the conversation, but local tests decide whether the model survives in real projects.
The business angle is also clear. Enterprises often want the control of owning or fine-tuning a model, but they do not necessarily want to maintain the full training stack. Inkling plus Tinker points to a split: the weights create portability and trust, while the managed fine-tuning platform captures repeated work around adaptation, evaluation, and deployment. If that loop is smooth, the model does not have to beat every closed frontier system to be useful.
The release still needs time in the field. A first model can impress in demos and disappoint inside domain-specific workflows, especially when audio, reasoning controls, and agent use are involved. But Inkling gives the open-weight race a sharper question. The contest is no longer only “which model tops the board?” It is also “which model can a team realistically bend toward its own task without surrendering control?”
Related Articles
A high-scoring r/LocalLLaMA thread surfaced Qwen3.5-397B-A17B, an open-weight multimodal model card on Hugging Face that lists 397B total parameters with 17B activated and up to about 1M-token extended context.
LocalLLaMA reacted like dense models had suddenly become fun again. The official Qwen numbers were strong, but the real community energy came from people immediately asking about quants, GGUF builds, and whether 27B had become the practical sweet spot. By crawl time on April 25, 2026, the thread had 1,688 points and 603 comments.
The thread’s energy centered on the architecture claim: what does “encoder-free” really mean for a 12B multimodal model?