Inkling vs Qwen 3.8

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 Inkling and Qwen 3.8, side by side, on 41 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.

Inkling · Benched on GoldieBench one-shot through Tinker's OpenAI-compatible endpoint at medium reasoning effort, then headless-playtested on the same rubric as the whole field. In the Agent OS it's wired into the opencode tab on your own Tinker key — the Ink Machine.

Qwen 3.8 · Benched on GoldieBench via the Qoder CLI (`qoder-qwen`, model Qwen3.8-Max-Preview) — the only door while it has no public API. Non-game tasks are one-shot like the rest of the field. GAME tasks run in Qoder's real AGENT mode: skill-infused build, then up to 2 QA fix rounds where a vision judge + live console errors are fed back and Qwen 3.8 edits its own file (it took crypt from a black-screen 3.0 to a torch-lit 7.8). Scored on a mid-play frame by the same Opus judge as everyone else. This is a partial run — the full 50-task card replaces it when the batch completes.

Where Inkling beat Qwen 3.8

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

Where Qwen 3.8 beat Inkling

The tasks where I gave Qwen 3.8 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 41 scored shared tasks, Qwen 3.8 averaged 8.22/10, beating Inkling's 5.96/10 by 2.26 points. Pick Qwen 3.8 when the build has to ship on the first prompt and you can afford the trade-offs in the comparison below.

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 Inkling and Qwen 3.8 both into the Agent Operating System and dispatch each from the kanban by task type — owning a frontier model instead of renting one — on your own key, pennies per build → Inkling, one-shot 3d game and world prototypes where atmosphere matters → Qwen 3.8. That's the same setup I run for the 4,000+ founders inside the AI Profit Boardroom.

FAQ — Inkling vs Qwen 3.8

Which is better, Inkling or Qwen 3.8?

On Goldie Bench, Inkling averages 5.96/10 across the shared tasks, with 0 gold, 0 silver, 0 bronze overall. Qwen 3.8 averages 8.22/10, with 10 gold, 9 silver, 5 bronze. Qwen 3.8 wins the head-to-head 38–2.

How much does Inkling cost vs Qwen 3.8?

Inkling: Inkling is open-weights — a 975B-parameter (41B active) Mixture-of-Experts model whose full weights are public on Hugging Face. You run it on your own key through Tinker's OpenAI-compatible endpoint (usage-based, ~$0.33/M sampling, 50% off at launch), or via Together / Fireworks / Modal / Databricks / Baseten. Benched here one-shot at medium reasoning effort via Tinker. Qwen 3.8: Qwen3.8-Max-Preview is Alibaba's ~2.4T-parameter flagship, positioned just behind Claude Fable 5. It is NOT on OpenRouter or a public API yet — the only access today is inside Qoder (Alibaba's agentic coding platform, free 2-week Pro trial). Benched here via the Qoder CLI on model `Qwen3.8-Max-Preview`, one-shot.

What's the context window for Inkling vs Qwen 3.8?

Inkling has a 1,000,000 tokens context window. Qwen 3.8 has a Served through Alibaba's Qoder agent platform; the 3.8-Max preview has no standalone public context window yet. context window.

When should I pick Inkling over Qwen 3.8?

Pick Inkling for: Owning a frontier model instead of renting one — on your own key, pennies per build; Generative visuals, data-viz and single-file web builds you want one-shot; A customizable open base you can fine-tune on Tinker for your own domain. The trade-off is the weaknesses we logged on the bench: One-shot 3D games are weak — three.js dungeons/racers render a title screen but no playable scene, like most open models (crypt 2.5); Physics and particle sims are hit-or-miss — black-hole, plasma and cloth one-shots often render dark or static (2.3–3.5); Not the strongest overall — the closed frontier (Fable 5) still tops the raw benchmarks; Inkling trades peak for ownership.

When should I pick Qwen 3.8 over Inkling?

Pick Qwen 3.8 for: One-shot 3D game and world prototypes where atmosphere matters; Anyone already in the Qoder IDE/CLI wanting a near-frontier model free on the Pro trial; A cheaper stand-in for Fable 5 on creative-visual builds. The trade-off is the weaknesses we logged on the bench: Torch-lit dungeon (crypt) came out generic (6.3); one open-world RPG one-shot black-screened (twilightvale 2.5) — classic three.js r128 API drift; Preview is Qoder / Token-Plan only — no OpenRouter or public API, so it can't be routed into an app the way the OpenRouter models can.

How does Goldie Bench score Inkling vs Qwen 3.8?

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: Inkling · Qwen 3.8 · back to the leaderboard