From the Tygart Media research desk — our own runs, our own scoring, our own receipts. Part of the GLM Desk.
Every AI model ships with settings nobody tests. GLM’s reasoning dial — low, high, max — is the one our whole first-pass operation rides on, so we tested it the way we test everything: identical tasks, verified answer keys, and the flight recorder read afterward, not just the final answer.
The finding is not “max is better.” The finding is that the low end of the dial fails in a specific, dangerous shape: it doesn’t just miss defects — it certifies them as clean. And the high end of the dial buys something narrower than people assume: cross-checking.
What the dial is
GLM’s current models accept a reasoning effort setting with three stops — low, high, max — and max is the default; per the model’s own documentation, any value outside the three also falls back to max. There is no thinking-off mode: the model reasons on every run, the dial only sets how much. Most coverage of GLM never touches this dial at all. Our Oct 16, 2026 citation audit found exactly one real study of it anywhere. This is the second, and it’s run on production-shaped work, not benchmarks.
The test
We took three tasks from our scored limit battery — tasks with answer keys verified against source material — and ran each at the default setting and again with the dial forced low. Same briefs, same seat, same scoring.
| Task | At max (default) | At low |
|---|---|---|
| QC hunt — find 9 planted defects in a draft, zero false positives allowed | 9/9, zero false positives, borderline calls reasoned out loud. 46 seconds. | 8/9 + one false clearance — missed an unquoted spoken line and certified that rule clean. 9.1 seconds. |
| Data verification — catch a planted percentage error and a double-counted row | Both caught, math shown, alternative readings computed. | Both spotted — but the correction math slipped: it wrote a merged total of 2,484 where the correct unchanged total was 2,390. |
| Stamina census — 15 pages, 60 exact fields (titles, headings, embeds) | 60/60. 121 seconds. | 60/60. 56 seconds — same accuracy, half the time, cheaper. |
Read the table the way an operator would. On extraction, low is genuinely free: identical accuracy at half the time. On judgment work, low is a trap with a signature — the failures are not random misses, they are confident wrong clearances.
Why low fails that way: the recorder’s answer
The final answers alone would have told us low “mostly works.” The flight recorder told us the mechanism. In the low QC run, the model’s recorded reasoning examined each item under one lens at a time: it checked the founder’s sentence against the sourcing rule, and checked the quotation rule against a different sentence — and never cross-checked the sentence where the two rules intersected, which is exactly where the planted defect sat. One lens per item, then a clean bill of health.
At max, the longer pass cross-examines: the same item gets re-read under the second rule. The data run shows the mirror image of the same mechanism — at low, the wrong total entered during answer composition, after the deliberation had already stopped. The thinking ended; the writing continued; the error moved in.
That’s the dial’s real trade. Low doesn’t buy a dumber model. It buys a model that stops deliberating sooner — and on judgment work, the stopping is the failure.
The rule we run
Three working rules came out of this battery, and they now govern every GLM launch in our fleet:
1. Extraction and census work can run low. Identical accuracy (60/60), roughly half the time. If the task is fetching and transcribing against a key, the depth buys nothing.
2. Judgment work never runs low. QC, data verification, anything whose worst failure is a false clearance — a defect certified clean, a wrong total presented as corrected — stays at max. A miss you can see is a cost. A miss the model has stamped “checked” is a liability.
3. The setting is set explicitly, every launch. Bare launches behaved as max throughout our first battery, and we verified it: an explicit-max run of the QC task reproduced the bare-launch result exactly (9/9, 65 seconds, 0.58¢). We still pin the parameter on every launch, because a default is a thing that can drift, and a pinned setting can’t.
What we haven’t tested
High as a standalone middle setting is untested — low and max bracket it, and we’d rather say that than interpolate. Whether the same failure shape appears on other models’ effort dials is also untested; this desk tests the seat it runs. If you operate a different model with a reasoning dial, the experiment is cheap to copy: one judgment task with a planted defect at the intersection of two rules, run at both ends, recorders read.
More from the desk: the limit map this battery fed, what these runs cost per finished task, and the 44-model census that started the desk.
The settings box
Seat: GLM 5.3 Flash, Cursor cloud agents, no code repository. Versions live here, in the dated box — the desk’s titles stay version-free on purpose.
Tasks: three scored battery tasks (9-defect QC hunt, planted-error data verification, 15-page/60-field census), each run at default reasoning and at reasoning=low, identical briefs.
Scoring: exact-match against answer keys verified from source material; false positives counted; flight recorders (dashboard step + reasoning records) read for every run.
Date: October 16, 2026. Cost: the six dial-probe runs cost 2.2¢ total, as recorded by the platform.
Leave a Reply