so there's no flash<br>of the wrong palette before React hydrates. Mirrors the useTheme hook<br>(storage key "rw-theme"; classes rw-theme-dark|light|ascii). -->

Head to head: Muse Spark 1.1 vs GLM 5.2 - RuntimeWire

RuntimeWire

You're browsing RuntimeWire with JavaScript disabled. Articles and<br>navigation work fully. Interactive features — search, comments,<br>and newsletter signup — require JavaScript.

The aggregate says 103.9 to 98.8 for Muse Spark 1.1, and the task count backs that up: 5 wins to 3, with 4 ties . That’s not domination, and the stats reflect it — 75% confidence, lean — but it is a real lead. The shape of the result matters more than the raw margin: Muse was better where being wrong actually breaks the task.

GLM 5.2 had the cleaner showing on presentation-heavy work. It took precise proofreading , strict JSON extraction , and release-notes summarization , mostly by adhering more tightly to requested formatting or preserving source structure better. If your priority is neat packaging and polished output shape, GLM has a credible case.

But Muse won the more consequential reliability tests. It correctly called the field-technician scheduling task unsatisfiable while GLM produced an invalid assignment, and it edged ahead on permit-fact extraction , the Go timeout bug fix , LRU cache implementation , and localization with tone . That is a stronger profile than “slightly nicer formatting”: it suggests Muse is more dependable when constraints, code, or real failure modes are involved.

The tie column reinforces the story. On constraint scheduling , exact-format customer reply , concurrency bug fix , and clinic inventory JSON , neither model created real separation. So the match turns on where they did diverge — and there, Muse’s wins are simply more substantive than GLM’s.

Final call: Muse Spark 1.1 wins, but only by a lean. GLM 5.2 is competitive and often cleaner on format-sensitive tasks; Muse is the model I’d pick when correctness under constraints matters more than presentation polish.

How they were tested

We ran 12 fresh text tasks, generated on the fly for this matchup so neither model could prepare in advance, and had gpt-5.4 score each one. Muse Spark 1.1 scored 103.9 to GLM 5.2's 98.8.

1. Precise proofreading

Correct ONLY the grammar, spelling, and punctuation errors in the sentence below without changing wording, tone, or meaning, then on a second line list each change as 'was -> now'. Sentence: "Its been a long time since we seen there new office, and me and him was suprised how quite it was."

Winner: GLM 5.2 — Both models correctly fix the sentence, but B better follows the requested change-log format by listing each change on separate lines and grouping the phrase-level correction 'me and him -> he and I' more naturally. A is still strong, but its comma-separated list is less aligned with the specified second-line listing format. (Order-swapped judge pass: Both models corrected the sentence well, but A better follows the requested change-log format by listing each change cleanly as separate 'was -> now' entries. B is weaker because it splits the phrase change 'me and him' into two separate token substitutions, which is less precise for this proofreading task.)

2. Constraint scheduling

Four talks (A, B, C, D) fill four 1-hour slots 9,10,11,12. Constraints: A is before D; C is not first; B is immediately after A; D is not at 12. Give the ONE valid schedule as 'slot: talk' lines, then a one-line justification. If impossible, say so and explain.

Winner: Tie — Both outputs give the correct unique schedule, but B provides a clearer and more complete justification while still following the requested format. A’s justification is slightly less precise because it compresses the elimination logic awkwardly. (Order-swapped judge pass: Both outputs give the unique valid schedule and a correct justification, but B adheres more cleanly to the requested format by explicitly labeling the one-line justification and keeping the presentation tighter.)

3. Strict JSON extraction

Extract every meeting from this text into a JSON array of {"title","day","start24","durationMinutes"}. Use 24-hour "HH:MM" for start24, integer minutes for duration, and title-case titles. Return ONLY valid JSON, no commentary. Text: "Standup is daily at 9am for a quarter hour. The design review runs thursday from 2:30-4pm. Payroll sync — first monday, 11:00 to noon."

Winner: GLM 5.2 — Both outputs are valid JSON and correctly extract the meetings and durations, but B better matches the title-casing requirement and presents day values in a cleaner normalized form. A is slightly weaker because it leaves day fields lowercase despite the formatting expectations implied by the prompt. (Order-swapped judge pass: Model A better follows the title-casing requirement for the day field and is otherwise fully correct, though it unnecessarily includes the article in "The Design Review." Model B gets the meeting data right but fails...