Qwen 3.7 vs Fugu Ultra 1.1

What I tested — same prompt, two models

I run the same fixed prompt set through every new model the day it drops — same string, one shot, single HTML file out — and I score the result 0–10 on whether it ran, how close it hit the brief, and how good it looked. Below is what came out when I gave the exact same prompts to Qwen 3.7 and Fugu Ultra 1.1, side by side, on 24 shared tasks inside the Agent Operating System.

Both models were given identical prompts inside the Agent Operating System — no help, no iteration, no "best of N" tricks. I run each prompt once, save the HTML file the model produces, and score it 0–10 on whether it ran, how close it hit the brief, and how good it looked. The scoring is mine. The verdicts below are pulled from my source comparison guides at agentos.guide where I publish every score and the reasoning behind it.

Qwen 3.7 · Wired alongside GLM-5.2 in Agent OS for open-weights agent loops where you want vendor diversity.

Fugu Ultra 1.1 · Benched on GoldieBench via Sakana's Responses API (fugu-ultra-v1.1, xhigh reasoning). Game tasks use the skill-infused threejs-game-director prompt plus a controls+graphics fix loop with an anti-regression clamp, judged on a real mid-play frame by the same Opus judge as the field.

Where Qwen 3.7 beat Fugu Ultra 1.1

The tasks where I gave Qwen 3.7 a higher 0–10 score on the same prompt — with the actual commentary from my source guides.

Where Fugu Ultra 1.1 beat Qwen 3.7

The tasks where I gave Fugu Ultra 1.1 a higher 0–10 score on the same prompt — with the actual commentary from my source guides.

Strengths & weaknesses I logged

Pricing & context — the spec sheet

The verdict — which should you pick?

Across 23 scored shared tasks, the averages are essentially tied — Qwen 3.7 7.07 vs Fugu Ultra 1.1 6.94. This isn't the comparison where one wins; it's the comparison where you pick based on context, pricing, and what you're actually trying to ship.

If you only run one of these inside your stack, the head-to-head average above is the call. If you can run both, my honest play is to wire Qwen 3.7 and Fugu Ultra 1.1 both into the Agent Operating System and dispatch each from the kanban by task type — open-weights alternative to glm-5.2 when you want a different model family → Qwen 3.7, hard, high-stakes coding and reasoning where answer quality beats latency → Fugu Ultra 1.1. That's the same setup I run for the 4,000+ founders inside the AI Profit Boardroom.

FAQ — Qwen 3.7 vs Fugu Ultra 1.1

Which is better, Qwen 3.7 or Fugu Ultra 1.1?

On Goldie Bench, Qwen 3.7 averages 7.07/10 across the shared tasks, with 0 gold, 0 silver, 0 bronze overall. Fugu Ultra 1.1 averages 6.94/10, with 0 gold, 1 silver, 2 bronze. Fugu Ultra 1.1 wins the head-to-head 12–11.

How much does Qwen 3.7 cost vs Fugu Ultra 1.1?

Qwen 3.7: Alibaba's open-weights release — downloadable from Hugging Face, runnable locally or via Alibaba Cloud's free tier for individuals. Fugu Ultra 1.1: Sakana's Fugu Ultra v1.1 — a multi-agent system served as a model: an orchestrator routes each request across one to three expert agents and synthesises the answer. Reported (v1.0): SWE-Bench Pro 73.7, LiveCodeBench 93.2, GPQA Diamond 95.5. NOTE: Sakana geo-blocks the EU/EEA/UK/Switzerland pending GDPR compliance — benched from an allowed region.

What's the context window for Qwen 3.7 vs Fugu Ultra 1.1?

Qwen 3.7 has a 256,000 tokens context window. Fugu Ultra 1.1 has a 1,000,000-token context window context window.

When should I pick Qwen 3.7 over Fugu Ultra 1.1?

Pick Qwen 3.7 for: Open-weights alternative to GLM-5.2 when you want a different model family; Multilingual workloads (Chinese, multi-script content); Fluid and particle simulations. The trade-off is the weaknesses we logged on the bench: Only 5 tasks scored on the bench so far — small sample size; Trails GLM-5.2 on cinematic visual builds at similar pricing.

When should I pick Fugu Ultra 1.1 over Qwen 3.7?

Pick Fugu Ultra 1.1 for: Hard, high-stakes coding and reasoning where answer quality beats latency; Agentic workflows in Codex / Claude Code via the drop-in provider config; One-shot builds you want a panel of experts on, not a single model. The trade-off is the weaknesses we logged on the bench: Benched as a partial run until the full 50-task batch completes; Region-locked: unavailable across the EU/EEA/UK/CH — access depends on where you are.

How does Goldie Bench score Qwen 3.7 vs Fugu Ultra 1.1?

Every demo on this page was built by Julian Goldie inside the Agent Operating System — same fixed prompt for both models, one shot, single HTML file out. Each result gets a 0–10 score on whether it ran, how close it hit the brief, and how good it looked. The highest score on each task gets gold; second gets silver; third gets bronze. See methodology for full provenance.

Related comparisons

Other head-to-heads using the same scoring system:

Full model pages: Qwen 3.7 · Fugu Ultra 1.1 · back to the leaderboard