Live data from Hacker News

Laguna S 2.1

poolside.ai

31–40 of 98 posts

Re: Laguna S 2.1

#31
post #12

I love this. Is it possible to give a feel of how this stacks up to the good old Opus 4.5 in coding quality? For me that was the turning point where agentic coding in Claude Code etc became usable. Have we hit that threshold?

Having played with it for like 3 hours now....I'm probably moving from CC to this

One hour in, no more Codex for me. This thing rips.

Re: Laguna S 2.1

#33
post #19

Earlier quoted context omitted.

What harness/quant did you use for testing?

nvfp4 mlx, literally barebones pi. edit: on bigger tests, got it to loop pretty easily unfortunately, probably local settings.

What inference server are you using? They have a custom branch for llama.cpp, but I wouldn't be surprised at all if it still needs fixing.

Re: Laguna S 2.1

#34
!! Be careful when testing the model.

A lot of people are testing it, and reporting disappointed results / benchmaxxxing claim. But do not realize that thinking has a issue with the default configuration.

Important - make sure that THINKING is enabled. By default it wasn't although I was passing the flag --default-chat-template-kwargs '{"enable_thinking": true}' in vllm recipe. The generation_config.json file that is included has by default max_new_tokens as 32k which seems to be cutting off thinking altogether so increase it. At first I was very disappointed with the output I was seeing, but once thinking is enabled, the code quality seems to be MUCH better. More real world testing to be done.

https://www.reddit.com/r/LocalLLaMA/comments/1v2pg99/laguna_...

Re: Laguna S 2.1

#36
post #29
post #23

Looks impressive, and this size fits achievable home hardware. That said, if someone would kindly quantise this down for the 64GB paupers, that would be appreciated. (I know there’s likely degradation, but some people reported good results with a 2 bit version of Qwen 3.5 122B, and this is starting from a higher point. Would be interesting to try, at least.) Edit: someone in the process of doing so: https://huggingfa…

They have also published smaller 33B model called Laguna XS 2.1, its Q4 gguf is 20GB. https://huggingface.co/poolside/Laguna-XS-2.1-GGUF/tree/main

Thanks for flagging. From the few benchmarks I can find, it looks there or thereabouts with Qwen 3.6-35B-A3B, or maybe a touch below. I'm interested to compare a model that is a big jump larger with pretty impressive benchmarks, but more heavily quantized to fit.

Re: Laguna S 2.1

#38

!! Be careful when testing the model. A lot of people are testing it, and reporting disappointed results / benchmaxxxing claim. But do not realize that thinking has a issue with the default configuration. Important - make sure that THINKING is enabled. By default it wasn't although I was passing the flag --default-chat-template-kwargs '{"enable_thinking": true}' in vllm recipe. The generation_config.json file that is…

Even the official provider on OpenRouter seems to have this issue. Hope it's an easy fix for them.

Re: Laguna S 2.1

#39
Really impressive signal that this 128B model can beat DeepSeek V4 (1.6T) on most coding benchmarks!

Also, I really like Poolside's habit to compare not only to other top models in its weight class (others don't do it, looking at you Mistral), but also to the very top open-weight models, even much bigger ones like the 2.5T Kimi-K3!

Re: Laguna S 2.1

#40
post #33

Earlier quoted context omitted.

nvfp4 mlx, literally barebones pi. edit: on bigger tests, got it to loop pretty easily unfortunately, probably local settings.

What inference server are you using? They have a custom branch for llama.cpp, but I wouldn't be surprised at all if it still needs fixing.

This: https://github.com/Blaizzy/mlx-lm/tree/pc/add-lg ...and this is what I should probably wait for (not sure why it's in vlm): https://github.com/Blaizzy/mlx-vlm/tree/pc/laguna-s-nvfp4 ...or perhaps I should've just used the gguf with the provided llama.cpp instead of trying to run the nvfp4-mlx from the get go, but where's the chaos in that :)

Running deepseek flash on something locally now, this will have to wait a bit. I still stand by my initial quick assessment - looks capable. Some people on r/localllama also reported loops. We'll see in ~10 hours. Hopefully I haven't terribly mislead people.

Post reply on HN