Muse Wonder vs Claude Opus 5.5, GPT-6.1 Sol and Gemini 4 Argon

Meta released Muse Wonder on 12 October. On 16 October I ran it through my quick suite in Cursor CLI, beside Claude Opus 5.5, GPT-6.1 Sol and Gemini 4 Argon. This is Muse Wonder, not Muse Wonder Full, which Meta offers only in its Muse Code app.

Speed#

Time to finish

Seconds from starting the tool to its exit, one short explain task. Lower is better.

Median runseconds01020Muse Wonder15.8Claude Opus 5.516.7GPT-6.1 Sol9.3Gemini 4 Argon17.0Fastest runseconds0102012.511.99.116.0
ModelToolRun 1Run 2Run 3Run 4Run 5Run 6
Muse WonderCursor CLI27.0 s12.5 s13.7 s15.8 s15.7 s16.4 s
Claude Opus 5.5Claude Code16.4 s19.4 s18.5 s11.9 s16.9 s16.4 s
GPT-6.1 SolCodex CLI9.8 s9.1 s9.3 s9.3 s9.2 s11.7 s
Gemini 4 ArgonCursor CLI17.4 s16.7 s129.2 s16.3 s16.0 s26.0 s

The table scrolls sideways on a small screen.

Source: Daily Driver Bench at dailydriver.brenhq.com, updated 16 October 2026. 24 runs, six per model, medium effort, each in its own tool.

Output speed

Tokens per second while each answer streamed, a walkthrough of at least 600 words. Higher is better.

Tokens per secondmedian, o200k tokens075150Muse Wonder110Claude Opus 5.5115GPT-6.1 Sol47Gemini 4 Argon80Answer lengthmedian, o200k tokens01,5003,0001,8981,8651,3272,057

Source: Daily Driver Bench at dailydriver.brenhq.com, updated 16 October 2026. 24 runs, six per model, medium effort, each in its own tool.

  1. Muse Wonder: 12.5 to 27.0 s
  2. Claude Opus 5.5: 11.9 to 19.4 s
  3. GPT-6.1 Sol: 9.1 to 11.7 s
  4. Gemini 4 Argon: 16.0 to 129.2 s

Cost#

Cost and time per run

Real app work, median run at list prices. All four fixed every bug and passed every ticket test. Lower left is cheaper and faster.

  • Estimated frontier: no other model was both cheaper and faster

Bug hunt

$0.2$0.5$10246810Cost per run (USD), log scaleMinutes to finishMuse WonderOpus 5.5GPT-6.1 SolGemini 4 Argon

Tickets

$0.1$0.2$0.5$10246810Cost per run (USD), log scaleMinutes to finishMuse WonderOpus 5.5GPT-6.1 SolGemini 4 Argon

Source: Daily Driver Bench at dailydriver.brenhq.com, updated 16 October 2026. Real app work, 24 runs, medium effort, each model in its own tool.

Every check#

The same checks for all four.

CheckMuse WonderClaude Opus 5.5GPT-6.1 SolGemini 4 Argon
Four small coding tasks, every setup: runs that passed60 of 6060 of 6060 of 6060 of 60
ASD-STE100 instruction on the explain task: runs that passed3 of 33 of 33 of 33 of 3
Bug hunt: bugs fixed of 20, each run20, 20, 20 of 2020, 20, 20 of 2020, 20, 20 of 2020, 20, 20 of 20
Bug hunt: runs that edited the existing tests0 of 30 of 30 of 31 of 3
Bug hunt: estimated cost per run at list prices, median$0.51$0.78$0.22 to $0.25$0.52
Tickets: hidden tests passed, each run17, 17, 17 of 1717, 17, 17 of 1717, 17, 17 of 1717, 17, 17 of 17
Tickets: estimated cost per run at list prices, median$0.75$0.96$0.20 to $0.22$0.70

The table scrolls sideways on a small screen.

Every run counts. A run that edits an existing test fails, whatever else it fixed. Runs from Muse Wonder 16 October, Claude Opus 5.5 22 to 30 September, GPT-6.1 Sol 29 to 30 September and Gemini 4 Argon 13 October, 2026.

How I ran it#

Background and method

Muse Wonder and Gemini 4 Argon ran in Cursor CLI 2026.10.01-e373342 as Cursor's medium versions, Claude Opus 5.5 in Claude Code 2.1.284 and GPT-6.1 Sol in Codex CLI 0.159.0, all at medium effort. All four ran in Docker on my subscriptions, with no API keys.

Time to finish is the whole run on one short explain task, from starting the tool to its exit, so it includes start-up. A run passes when the answer names the month logic and the ValueError.

Output speed comes from a separate session, a walkthrough of at least 600 words, six runs each. I saved each answer, counted it with OpenAI's o200k tokenizer and divided by the seconds from its first answer token to its last. I timed Claude Code's tokens at a local proxy, Codex's on its WebSocket and Cursor's on its own stream, so buffering can shift the rates. Start-up, reading the file and thinking are left out. OpenAI's own count for Sol's answers is within 0.5% of the o200k count. Anthropic counts Opus 5.5's answers as about 1.4 times as many tokens. A run counts when it passed and streamed in 20 or more pieces, and a median needs three; every run counted.

The checks are four small coding tasks with no skill, a placebo file and three token-saving skills, three runs each; the ASD-STE100 instruction on the explain task; and a bug hunt with 20 planted bugs and three sprint tickets in a small TypeScript app, graded by hidden tests. Opus 5.5, Sol and Argon use their published runs of the same tasks.

Costs are list-price estimates from each run's tokens. Muse Wonder is $4 per million input tokens, $0.20 cached and $20 output, the same as Claude Opus 5.5, and Meta lists no cache-write price. Gemini 4 Argon is $2, $0.10 and $10 until 30 November 2026, then double. Opus 5.5's cost includes cache writes at twice its input price. Muse Wonder and Opus 5.5 have the same list prices. Most of the gap is Opus 5.5's cache writes, 53,000 to 58,000 tokens a run at twice its input price. Cursor reports none for Muse Wonder. Muse Wonder also wrote fewer output tokens, 13,000 to 18,000 a run to Opus 5.5's 16,000 to 21,000. Sol's is a range because Codex logs no cache writes. I paid through subscriptions, not these amounts.

The run records are in results.json, under launch28_timing, launch28_runs and launch28_real_runs, with Gemini 4 Argon's under launch27_runs and launch27_real_runs, and Opus 5.5's and GPT-6.1 Sol's under runs, ste_runs and bughunt_runs.