65
submitted 1 day ago* (last edited 1 day ago) by Shatur@discuss.tchncs.de to c/localllama@sh.itjust.works

From Unsloth's post on Reddit:

Hey guys Thinking Machines released Inkling 2 Mini, the strongest 26.4B model (regardless if MoE or dense) that runs on ~16GB RAM.

Inkling 2 Mini is Thinking Machines Lab’s new 26.4B MoE (5.4B active) model for coding, agentic & vision workloads.With a Looped Transformers architecture and 1M context, it scores 48.2% on DeepSWE v1.1 and 77.9% on SWEBench Pro v2 (Hard), the highest for its size. Thanks TML for day 0 access.

Run on Unsloth Desktop or llama.cpp.

GGUF: https://huggingface.co/unsloth/Inkling-2-Mini-GGUF

Guide: https://unsloth.ai/docs/models/inkling-2-mini

But looks like the model is not available in llama.cpp yet:

But if benchmarks are true, it's somewhat on par with Qwen 3.8 27B!

top 10 comments
sorted by: hot top new old
[-] e0qdk@reddthat.com 7 points 15 hours ago

I've got it running with the latest version of llama.cpp compiled from source + my own Q6_K quant. The safety is cranked up to the point that it's almost useless, and it's disappointingly sluggish for a MoE model of this size -- at least with the settings I've tried so far (which were pretty good for Qwen and gemma4).

I'm curious to see what comes of this after the abliterators get acquainted with it and the llama.cpp developers have a bit more time to poke at it... but so far it's very meh.

[-] afterate@sh.itjust.works 5 points 9 hours ago

I heard the same thing from other people online. I think that's why Alibaba began releasing 'NEXT' Qwen models so that the community could take time to work out the kinks.

[-] Shatur@discuss.tchncs.de 4 points 13 hours ago* (last edited 11 hours ago)

What are you guys doing to trigger the safety rails? 😅

[-] librekitty@lemmy.today 14 points 1 day ago

a moe model designed for 16gb ram? christmas came early! 🎁

[-] FaceDeer@fedia.io 6 points 22 hours ago

Ooh! Qwen4 will need to knock it out of the park, it's nice to have competition keeping things moving. :)

[-] BeefAndPoultry@lemmus.org 13 points 1 day ago* (last edited 1 day ago)

woa it's even beating dense models, no way it's actually that good

once those llama.cpp pull requests are merged I'll try it out

I wonder how the looped layers interact with --moe-cache-mib

[-] EasyPeasy@piefed.zip 3 points 1 day ago

One of the PRs is merged now, although not the unsloth one so personally I am trying the ggml-org weights first to be on the safer side. With a novel architecture and looping layers I wouldn't rule out a few days of problems to iron out in the implementation though...

[-] Shatur@discuss.tchncs.de 4 points 11 hours ago

According to reports it's not very stable in llama.cpp right now. Unsloth fixed it in their fork, so yeah, I'd wait a little.

[-] panda_abyss@lemmy.ca 7 points 1 day ago

Looks promising

[-] panda_abyss@lemmy.ca 4 points 1 day ago

This is what happens when Qwen strings you along for weeks with delivering anything or even concretely stating the scope of the models they’ll release.

this post was submitted on 20 Nov 2026
65 points (95.8% liked)

LocalLLaMA

5703 readers
75 users here now

Welcome to LocalLLaMA! Here we discuss running and developing machine learning models at home. Lets explore cutting edge open source neural network technology together.

Get support from the community! Ask questions, share prompts, discuss benchmarks, get hyped at the latest and greatest model releases! Enjoy talking about our awesome hobby.

As ambassadors of the self-hosting machine learning community, we strive to support each other and share our enthusiasm in a positive constructive way.

Rules:

Rule 1 - No harassment or personal character attacks of community members. I.E no namecalling, no generalizing entire groups of people that make up our community, no baseless personal insults.

Rule 2 - No comparing artificial intelligence/machine learning models to cryptocurrency. I.E no comparing the usefulness of models to that of NFTs, no comparing the resource usage required to train a model is anything close to maintaining a blockchain/ mining for crypto, no implying its just a fad/bubble that will leave people with nothing of value when it burst.

Rule 3 - No comparing artificial intelligence/machine learning to simple text prediction algorithms. I.E statements such as "llms are basically just simple text predictions like what your phone keyboard autocorrect uses, and they're still using the same algorithms since <over 10 years ago>.

Rule 4 - No implying that models are devoid of purpose or potential for enriching peoples lives.

founded 3 years ago
MODERATORS