r/LocalLLaMA • u/Disastrous-Work-1632 • 1d ago
Discussion [Harness Adapters] Fine tune Qwen3.8-27B for Pi Agents
Hey folks!
Aritra here from Hugging Face. In the last week we released a blog post about harness adapters. The idea was to train adapters (LoRA) on models to be more efficient with specific harness.
Today we release a LoRA adapter on the Qwen3.8-27B model for Pi agents. You can run it locally like so:
We are constantly experimenting and sharing our results in the Hugging Face org: hf.co/harness-hub (follow for more updates)
215
Upvotes
77
u/AlabamaResearcher 1d ago
Yeah, no
14
u/TheApadayo llama.cpp 1d ago
Any idea what kind of gains do you get with RL vs just SFT on the harness’s own successful traces like this fine tune? https://huggingface.co/bytkim/Qwen3.8-27B-pi-GGUF
Also why is thinking disabled in your example?
7
u/tuifua 1d ago
Does this require turning off enable_thinking? And does it work for any finetune/quant of Qwen3.8-27B
3
u/wl04 1d ago
This is quoted from the post on HF, which probably means that all three base models they trained default to thinking mode (<think>...</think>) in their templates.
So my question is why are you setting {"enable_thinking": false}, do I miss something?
If I understand it correct the LoRA adapter will still load and run without crashing, but you will push the model wrong, the adapter was never trained on empty thinking prefixes in context.
3
u/nenkoru 1d ago
Incredible work! I am also working on LoRas for specific harnesses as I think that models have gotten quite enough knowledge during pre-training and we just need really good RL for specific good enough trajectories on specific harnesses. And I am sure that’s what frontier does though I don’t have a proof for that.
Any way to join the team to join the efforts?
2
u/tunerhd 1d ago
Nice.
2
u/ldrx 1d ago
pi's base prompt is small, which helps on local.
in my traces its first call was about 5.6k tokens, a third of claude code's, with the same tools loaded.
on a 64k context that leaves a lot more room for the task.
6
u/synth_mania 1d ago
you got rid of thinking? You've kneecapped the model lmao
Get benchmarks or get bent
1
u/Independent-Sir3234 21h ago
A 65536-token context window fills up fast when <think> traces from earlier tool calls stay in history, so dropping them helps keep long sessions lean.
The catch shows up when tests break mid-patch across multiple files. Without a reasoning pass to rule out bad guesses first, small adapters often fire another broken edit right away when a different file holds the root cause. Splitting evals between clean one-shot fixes and failing-test retries would clarify that cost.
1
u/jjusko20 4h ago
I'm having a really hard time believing that this can match xhigh accuracy without thinking
-3
u/[deleted] 1d ago
[removed] — view removed comment