I use GLM-5.2 as an orchestrator model which delegates to Deepseek subagents (v4 flash or pro depending on complexity) and it works pretty well for a quite complex compiler codebase when I do deep enough up front planning for features/fixes.

If you believe the benchmarks Deepseek v4 is pretty shitty at long running work in large codebases, but really really good at self contained algorithmic/math reasoning - which is basically ideal for a compiler for a language with a relatively complex type system. And with its cache pricing it's very cheap.

GLM-5.2 is too expensive at api pricing for my taste though even when it's not producing the bulk of the output tokens - I pay for the mid-tier subscription and switch the orchestrator over to other models via open router when I run out - Minimax M3 feels okay but definitely a step down from GLM-5.2.

I had a similar experience

very simlar experience.

I would also add that I run it this way ~12hour a day non-stop. 300M / tokens per day (99.7% cache hit).