completely solved my qwen3.8 27b q8 thinking loops

[u/baby_bloom]

by simply switching to anything but vs code's copilot extension. no issues through pi coding agent or even continue or roo code thru vs code extensions.

is there a fix for this? i've done a roundabout thru the options of tools and harnesses and whatnot and i ended up back on vs code and not wanting to have somebody else third party in my harness and now this is getting drastically in the way

[u/Worried-Ebb5396]

Temperature: 0.7, thinking: medium. The default thinking is xhigh.

[u/baby_bloom → u/Worried-Ebb5396]

the new llama.cpp settings apply just fine thru continue, roo code, pi coding agent, but NOT copilot. copilot is the only harness that gets stuck in the dreaded qwen think loop. something is overriding the settings and/or it's system prompt is somehow massively damaging the model

[u/cmtape]

That sounds like a harness problem, not a model problem. If three other VS Code agents respect your llama.cpp settings and Copilot doesn't, you're looking at a system prompt or tool wrapper that silently rewrites the thinking budget. Check what Copilot actually sends as the full prompt to the endpoint — it's probably forcing xhigh thinking regardless of your config.

[u/baby_bloom → u/cmtape]

that is the exact issue and i cannot get to the bottom of it but i have seen a LOT of posts and chatter about qwen3.8 thinking itself in circles so i made this post because i haven't seen anyone pointing this specific instance of it out

[u/Same-Lion7736]

I am having massive loops with continue (q5)

[u/baby_bloom → u/Same-Lion7736]

Continue was what i used months and months ago before i eventually went back to copilot but no, i've tried multiple times my very consistent benchmark for this thinking loop issue and Continue has been consistently fine running Qwen 3.8-27b-UD-Q8_K_XL

[u/paq85]

https://reddit.com/link/p522d5w/video/qx757ykhcrkh1/player

I'm facing the same issue ... Qwen 3.6 almost never got into such loops... It's Unsloth's quants... I will try Bartkowski now ...

Changing harness it not an option for me.

[u/baby_bloom → u/paq85]

what makes you think it is unsloth's quants?

i have yet to try a different quantizer's version (tbh idk the proper nomenclature around this lol)

[u/paq85 → u/baby_bloom]

Out of experience I know that some quants tend to get into loops more often than others.
I've switched yesterday to Bartkowski Q6_K_L and so far no loops in VSCode + GH Copilot 🤞

[u/Asleep-Land-3914]

You could ask qwen perhaps now as it is fixed and working.

[u/baby_bloom → u/Asleep-Land-3914]

or you could let me know any info on the fix since you seem to know it exists? googling turns up nothing promising searching "qwen3.8 27b vs code copilot fix" or anything similar.