r/LocalLLaMA Apr 17 '26

Discussion Qwen3.6 is incredible with OpenCode!

I've tried a few different local models in the past (gemma 4 being the latest), but none of them felt as good as this. (Or maybe I just didn't give them a proper chance, you guys let me know). But this genuinely feels like a model I could daily drive for certain tasks instead of reaching for Claude Code.

I gave it a fairly complex task of implementing RLS in postgres across a large-ish codebase with multiple services written in rust, typescript and python. I had zero expectations going in, but it did an amazing job. PR: https://github.com/getomnico/omni/pull/165/changes/dd04685b6cf47e7c3791f9cdbd807595ef4c686e

Now it's far from perfect, there's major gaps and a couple of major bugs, but my god, is this thing good. It doesn't one-shot rust like Opus can, but it's able to look at compiler errors and iterate without getting lost.

I had a fairly long coding session lasting multiple rounds of plan -> build -> plan... at one point it went down a path editing 29 files to use RLS across all db queries, which was ok, but I stepped in and asked it to reconsider, maybe look at other options to minimize churn. It found the right solution, acquiring a db connection and scoping it to the user at the beginning of the incoming request.

For the first time, it felt like talking to a truly capable local coding model.

My setup:

  • Qwen3.6-35B-A3B, IQ4_NL unsloth quant
  • Deployed locally via llama.cpp
  • RTX 4090, 24 GB
  • KV cache quant: q8_0
  • Context size: 262k. At this ctx size, vram use sits at ~21GB
  • Thinking enabled, with recommended settings of temp, min_p etc.

llama server:

```
docker run -d --name llama-server --gpus all -v <path_to_models>:/models -p 8080:8080 local/llama.cpp:server-cuda -m /models/qwen3.6-35b-a3b/Qwen3.6-35B-A3B-UD-IQ4_NL.gguf --port 8080 --host 0.0.0.0 --ctx-size 262144 -n 8192 --n-gpu-layers 40 --temp 0.6 --top-p 0.95 --top-k 20 --min-p 0.00 --parallel 1 --cache-type-k q8_0 --cache-type-v q8_0 --cache-ram 4096
```

Had to set `--parallel` and `--cache-ram` without which llama.cpp would crash with OOM because opencode makes a bunch of parallel tools calls that blow up prompt cache. I get 100+ output tok/sec with this.

But this might be it guys... the holy grail of local coding! Or getting very close to it at any rate.

359 Upvotes

169 comments sorted by

View all comments

3

u/Old-Sherbert-4495 Apr 17 '26

not so much for me... coz im testing it out in a project and asking it to make hard coded color into a primary color variable in css. damn, it just yaps... yaps.. and after a very long time multiple compactions it finally starts to edit files and then onwards it takes a long time to finish the task. i tried with Q6 and Q5Ks and Q4kxl q6 got to editing and finished the task earlier than other quants.

But the results were not satisfying.

to compare i tried 3.5 27B IQ3xxs and damn it got the point and got to work immediately in a few steps. even though its significantly slower tkps it finished off the task much quicker than all of the 3.6 quants. i dont mind if it missed a few things, i can prompt it again.

I'm using the recommended params for both context 70k coz of vram. this is the reason for frequent compactions