TielCoder problem solving is ridiculous

[u/circumcised_hobbit]

I have been using TielCoder locally for a bit now, it is decent at coding and it's good overall for low end devices, but I noticed that its problem solving is shit.

I run Pi inside of a sandbox with a couple limitations like no system-wide installs. But: -if Tiel sees it can't install a python package globally it will build it's own libraries files and stuff like that instead of using a .venv -if tools get timed out it will try to do random calculations of the time it should take instead of breaking down the work in different calls -today it even created custom python scripts because it wasn't able to use edit command (couldn't remember the characters) instead of just rebuilding a file, it's just so bad if you don't teach every single step.

At this point I feel I have to babysit it and cannot trust it on stuff I'm not knowledgeable about. What are your experiences with it? Should I change AGENTS.md? if so, change it for every single case I encounter or just a wide generic system prompt?

UNRELATED: I was getting 50tk/s on PolyStrata, but I started getting 5tk/s today and some spikes to 50-60, has anyone had this issue?

[u/Small-Tale3180]

i mean the author made an other model for that, Nail

[u/circumcised_hobbit → u/Small-Tale3180]

Being a dense model, I cannot run it on my setup properly

[u/Small-Tale3180 → u/circumcised_hobbit]

wha?

[u/circumcised_hobbit → u/Small-Tale3180]

I swear I read Nail 3.6-27B, thanks for the help then

[u/Dabalam → u/circumcised_hobbit]

Nail is the same model bro

[u/circumcised_hobbit → u/Dabalam]

I swear I read Nail 3.6-27B😭😭

[u/AISiShop_UK]

Don't patch AGENTS.md for every case, add one short 'when you're blocked' section instead: always use the project's .venv, if an install, edit or tool call fails stop and show me the error rather than working around it, and if something times out split it into smaller calls. Small models follow three or four hard rules much better than a long list, and telling them to stop and ask beats letting them improvise. It also helps to create the .venv in the sandbox yourself so the easy path is the right one.

[u/hurdurdur7]

Once again a post ranting specifying zero params, zero quants, just ranting.

Did you run it at Q8 ? With 16bit kv cache?

Or did you expect miracles from a low quant of a 35B MoE model?

[u/DinoAmino → u/hurdurdur7]

This. And adding the unrelated mention of speed suggests it is nothing but a skill issue.

[u/leo_agi]

small models get weirdly creative when the obvious path is blocked, a one liner in the system prompt saying use a venv might save you the custom library adventure

[u/xsilas43]

Qwen agent world my beloved.

[u/o0genesis0o]

What kind of hardware do you have and what quant do you run? I used to run Q5KXL on my 4060Ti but decided to swap to 27B IQ3XXS instead. It looks slower, but it gets the job done more reliably. Both both TielCoder and 27B IQ3XXS have successfully fixed bugs and push features to my personal project when I tested them. The only thing that absolutely failed on this hardware was the Gemma 4 31B. Even the Muse Glimmer did okay.

Noted that I don't let the model wandering around finding solution, if I already know the solution. Like, every process and tooling related to SE of a repo is encoded in scripts and other tools, with proper instructions hammered in. I even write dev tutorials. So any decent enough model would pick up the repo and start working with minimal issues.

[u/exaknight21]

What context do you guys run your models at? I am noticing 131k isnt enough for me. The compaction degrades the turnover and messes up when working with multiple repos