Fetching from the wire…
Top 5 · 2026-08-14 · source-backed
Writer launched Palmyra X6 on August 13 with a number that should reset how you think about agent COGS: 52% lower average cost, 48% better speed, 10% better quality. The model is a post-training variation of Z.ai's open-source GLM-5.2. A US enterprise SaaS vendor built its flagship on a Chinese open-weights base rather than calling a frontier lab's API.
But the model swap isn't where the savings came from. Writer's own research found harness changes cut cost roughly 40% on average and were a more reliable lever than model choice. Read that again. The scaffold beat the model.
Three independent results landed the same week saying the same thing from completely different directions. AI4AI at Test-Time (arXiv 2608.12307, Cheng Qian, Heng Ji, Silvio Savarese and co-authors) had a strong model rewrite a weak model's inference harness and watched theory-of-mind accuracy go from 0.49 to 0.91. No retraining, no parameter changes. The gains came from offloading unstable reasoning into deterministic code, benchmark-specific routing, and strict answer-format enforcement. Explicitly not from making the target model think longer or sample more. Weaker models saw the biggest gains, which makes harness engineering a direct substitute for distillation when you're stuck with the model you have.
SHAPER (arXiv 2608.11350) arrived at the identical thesis in embodied robotics, keeping model weights frozen and evolving reusable skills plus a context-code harness through rollouts in the target environment. Same conclusion, totally different field, same week.
And the flip side: GLM-5.3's Terminal-Bench 3.0 number was produced by Z.ai running the public benchmark under its own Claude Code configuration, three rollouts per task, generous limits. Not an independent reproduction. If the harness contributes as much variance as the model, then an agentic benchmark score without its harness spec is uninterpretable. Vendor agentic numbers are an upper bound now, not a measurement.
Here's what I'd actually do. Before you switch models to cut costs, audit your scaffold. How many round trips per task? Are you re-sending context that's already cached? Is unstable reasoning happening in the model when it could happen in a deterministic function? OpenAI's GPT-5.6 builder guide buried the same point: Sol at "low" reasoning beat GPT-5.5 at "high" with the harness held constant. Everyone's arriving at this from different angles and nobody's saying it loudly enough.
The model is the part you can't control. The harness is the part you can.
Each link below shares sources, entities, or timing with this story.
OpenAI released Codex / Shared entities / Same source domain / Shared topic / Earlier coverage
Linked by a graph relationship (OpenAI released Codex); both cover Bench, Chinese, Claude Code, GLM; reported by the same outlet (techcrunch.com).
OpenAI uses Claude Code / Shared entities / Same source domain / Shared topic / Earlier coverage
Linked by a graph relationship (OpenAI uses Claude Code); both cover Bench, Claude Code, Everyone, GLM; reported by the same outlet (arxiv.org).
OpenAI released Codex / Shared entities / Shared topic / Earlier coverage
Linked by a graph relationship (OpenAI released Codex); both cover August, Bench, Claude Code, Everyone; overlapping topics (code, cost, harness, same).
Linked by a graph relationship (OpenAI released Codex); both cover August, Claude Code, Everyone, GPT; overlapping topics (agentic, code, harness, model, same).
OpenAI released Terra / Shared entities / Same source domain / Shared topic
Linked by a graph relationship (OpenAI released Terra); both cover August, Explicitly, GLM, GPT; reported by the same outlet (arxiv.org).
Sam Altman works at OpenAI / Shared entities / Same source domain / Shared topic / Earlier coverage
Linked by a graph relationship (Sam Altman works at OpenAI); both cover Bench, GLM, GPT, OpenAI; reported by the same outlet (openai.com).
OpenAI released Codex / Shared entities / Same source domain / Shared topic / Earlier coverage / Tension
Linked by a graph relationship (OpenAI released Codex); both cover Bench, GPT, OpenAI, Terminal; reported by the same outlet (openai.com).
OpenAI released Codex / Shared entities / Same source domain / Shared topic / Earlier coverage
Linked by a graph relationship (OpenAI released Codex); both cover Chinese, GLM, GPT, OpenAI; reported by the same outlet (marktechpost.com).