When you say "kinda dumb" it's worth noting that the smaller coding models tend not to actually need system prompts. Qwen maybe more than Muse Glimmer, but Muse Glimmer is so absolutely tuned for one particular pattern (turn-by-turn agentic coding and assistance) that it will do it more or less without a prompt at all (except to set the reasoning level maybe). It feels to me like it only needs a prompt to do plan mode stuff.
I wanted to like Opencode but I can't, really. I am enjoying Pi slightly more because it's just way less convoluted and obscure.
FWIW I use Paseo for the GUI, which to some extent eliminates that aspect of decision fatigue; if you like Paseo's UI well enough, you can have it with almost any harness.
No other model I've used does this.
The most frustrating thing is that it expects to be able to "read" directories? I am increasingly wondering about modifying Pi's read tool so it returns a directory listing in that context.
I have had some difficulty getting it to have a nuanced understanding of how I want to manage git, but I am reaching the conclusion that it's me that needs to change there.
I will test Qwen 3.8 27B properly at some point, though (judging by the insane, empty noise making campaign that is going on on social media, Qwen 4 is near)
Note though that this for local models that can run on a 5090, so, kinda dumb models with a small context window. Also they might perform differently on a custom pi setup rather than the very feature rich ohmypi.
Mostly the runs just cause me to get decision fatigue so I typically just use opencode and let a frontier model choose whatever cheaper models it wants to orchestrate with, so long as it's one that's not on the same token budget.
P.S. I'd always wondered who it was that got caleb.software before I could... Outshot in a western duel!