GPT-5.4 minivsQwen3-Coder-Next
GPT-5.4 mini | Qwen3-Coder-Next | |
|---|---|---|
| Specifications | ||
ParametersA rough measure of how big the model is. More parameters usually means more capable and more expensive to run, though it is a poor guide on its own — a smaller, newer model often beats a larger, older one. | — | 80B |
Context windowHow much text the model can hold in mind at once — your question, any documents you attach, the conversation so far, and its own reply. Go past it and the earliest part falls out of view. | 400k | 256k |
| API pricingUSD per 1M tokens · lower wins · base tier | ||
Input priceWhat you pay for everything you send the model — your question, plus any documents or earlier conversation you include with it. | $0.75 | $0.30 |
Output priceWhat you pay for the text the model writes back. It is normally the dearer half: producing an answer costs more than reading one. | $4.50 | $1.50 |
Cached input priceA reduced rate for text you send over and over. If every request starts with the same instructions or the same document, the provider keeps a copy ready and charges less to read it again. | $0.075 | — |
Cheapest inputLowest input rate across third-party providers, excluding the lab itself. The cheapest endpoint may run a quantised build or a shorter context — see "Available from" on the model page. | $0.75Azure | $0.12Parasail |
Cheapest outputLowest output rate across third-party providers, excluding the lab itself. May come from a different provider than the cheapest input. | $4.50Azure | $0.80Parasail |
| BenchmarksPublished by one model only | ||
BullshitBench v2Nonsense detection — Given a confidently-worded but nonsensical prompt, does the AI spot that it makes no sense and push back — instead of playing along and inventing an answer? The score is how often it clearly called out the nonsense. Higher is better. | 32% | — |
ProgramBenchProgram reconstruction — The AI receives a working program and its documentation, then builds a replacement from scratch without the original source code, internet access or decompilation. The score is the percentage of 200 programs that pass every behavioral test. We record each model's best published mini-SWE-agent result, including higher reasoning efforts where available. Partial test-pass rates and almost-solved programs do not count toward this score. Equal scores share a rank here; the official board also uses partial progress to break ties. Higher is better. | 0% | — |
SWE-Bench ProAgentic coding — Can the AI fix real bugs in real software? It's handed actual problems from open-source projects and has to write code that genuinely solves them. Higher is better. | — | 44.3% |
SWE-Bench VerifiedCoding — Real coding tasks pulled from open-source projects — the AI has to find and fix actual bugs. A human-checked version of the original SWE-Bench. Higher is better. | — | 70.6% |
SWE-Bench MultilingualMultilingual coding — Like SWE-Bench, but the coding problems span many programming languages, not just one. Tests how broadly the AI can code. Higher is better. | — | 62.8% |
Supabase Evals · with skillsSupabase coding — Supabase's own open benchmark: a coding agent is dropped into a real Supabase project and asked to do real work — set up a schema, fix a broken security policy, debug an Edge Function — and every run is checked against a live Supabase stack. This is the headline number, where the agent has Supabase's own skills loaded, as most people building on Supabase would. The score is the share of scenarios it got right. Higher is better. | 65.2% | — |
Supabase Evals · no skillsSupabase coding — The same Supabase scenarios, but with none of Supabase's skills loaded — so it measures what the model already knows about building on Supabase, rather than how well it follows Supabase's supplied instructions. Higher is better. | 55.1% | — |
Terminal-Bench 2.0Agentic terminal coding — Can the AI work in a command-line terminal — running commands and finishing technical setup tasks the way a developer would? (Version 2.0 of the test.) Higher is better. | — | 36.2% |
BU BenchBrowser agent — Can the AI drive a real web browser to finish tasks — clicking, filling forms, and navigating sites the way a person would? Run by Browser Use on their BU Bench task set. Higher is better. | 36% | — |
Humanity's Last Exam · with toolsMultidisciplinary reasoning — Humanity's Last Exam — extremely hard expert questions across many subjects. “With tools” means the AI is allowed to search the web or run code while answering. Higher is better. | 41.5% | — |
OSWorld-VerifiedAgentic computer use — Can the AI actually operate a computer — clicking, typing, and using real apps — to finish tasks on its own? Higher is better. | 72.1% | — |
| Overview | ||
| Company | OpenAI | Qwen |
| Release date | Mar 17 2026 | Feb 3 2026 |
| Access | Proprietary | Open Weight |
Other comparisons
GPT-5.4 minivsClaude Fable 5.1Qwen3-Coder-NextvsClaude Fable 5.1GPT-5.4 minivsGemini 3.8 FlashQwen3-Coder-NextvsGemini 3.8 FlashGPT-5.4 minivsMuse Spark 1.3Qwen3-Coder-NextvsMuse Spark 1.3GPT-5.4 minivsGrok 4.6Qwen3-Coder-NextvsGrok 4.6GPT-5.4 minivsDeepSeek-V4.1-FlashQwen3-Coder-NextvsDeepSeek-V4.1-FlashGPT-5.4 minivsMistral Medium 3.5Qwen3-Coder-NextvsMistral Medium 3.5
Frequently asked questions
GPT-5.4 mini and Qwen3-Coder-Next don't publish scores on any of the same benchmarks, so there's no direct head-to-head comparison. Qwen3-Coder-Next is cheaper on both input and output: $0.30 vs $0.75 per million input tokens, and $1.50 vs $4.50 per million output tokens. Figures are base-tier rates. Qwen3-Coder-Next shipped 42 days before GPT-5.4 mini, so benchmark comparisons should account for the intervening progress.
Context windows are 400k (GPT-5.4 mini) vs 256k (Qwen3-Coder-Next). GPT-5.4 mini is proprietary, while Qwen3-Coder-Next is open weight.
Direct benchmark comparisons are unavailable — GPT-5.4 mini and Qwen3-Coder-Next don't publish scores on any of the same benchmarks.