Tested gemma4:e4b vs qwen3.6:35b on agentic coding tasks using QuantaMind — pretty eye-opening gap
I've been using QuantaMind (free desktop app) to properly benchmark local models before trusting them in any agent workflow. Ran the built-in Coding eval suite today on two Ollama models and the results were more dramatic than I expected.
**What I ran:**
- Eval: Built-in Coding collection (Easy tier, 5 agentic tasks)
- K = 5 (each task run 5 times to test consistency, not just one lucky pass)
- Backend: Ollama on my local machine (64 GB RAM)
- Decoys: off
**Results:**
| Model | Pass^(K) | Avg Steps | Effort | Top Error |
|---|---|---|---|---|
| gemma4:e4b (Q4_K_M) | 3/5 | 1.8 | 257 tok | FAKE DONE |
| qwen3.6:35b (Q4_K_M) | 5/5 | 1.8 | 447 tok | NONE |
**The thing that stood out:** both models took the same average number of steps (1.8). The difference wasn't how many actions they took — it was whether those actions were actually correct.
The "FAKE DONE" error on gemma is particularly bad for agentic use. It means the model claimed to complete the task before it actually ran all the required steps. That's a silent failure — in a real pipeline it would just look like a successful run.
qwen3.6:35b passed everything cleanly, but used significantly more tokens (~74% more). So there's a real cost trade-off depending on your setup.
**Tool I used:** quantamind.co — free macOS app, runs fully local, no data leaves your machine. Has a built-in agentic sandbox with anti-cheat rules (it specifically catches the fake-done pattern). Also has a context cliff probe and readiness verdicts if you want to go deeper.
Curious if others have seen the fake-done failure on smaller models, or if there are other 4B-class models worth testing against qwen3.6:35b on coding tasks.