早鸟价(12 月 25 日截止),订阅期间一直锁定:Go $10/月(原价 $20),Plus 用 Opus 5.5 只要 $30/月(原价 $50)立即订阅 →
文本对话1M 上下文

Qwen3.8 Flash

Qwen3.8 Flash 是一款专为编程、Agent 及长文档打造的高速模型。支持 1M 上下文。每百万 Token 输入约 $0.057,输出约 $0.193。

价格 / 100 万 token省 50%
官方AIReiter
输入$0.1143$0.0571
输出$0.3857$0.1929
缓存读$0.0143$0.0071
缓存创建$0.1429$0.0714
说明文档
输入
限制回复长度。推理模型也会把思考计入其中。
qwen3.8-flash
输出

A codebase you don't know is a risk, not a hurdle. The plan should burn down that risk in order: understand, run, trace, spike, then make the change small enough that "production-ready" is a property you can demonstrate, not a hope.

Here are the first five steps, with the evidence you collect at each.

Step 1 — Get it building and the baseline green (half day)
Read the README, the manifest(s), the CI config, and any architecture docs. Boot the app locally, run the full test suite, run the linter/typechecker.
Evidence: The exact commands that reproduce a clean build and a passing test suite from a fresh checkout (recorded output, not memory of it). A one-page map you wrote yourself: where the entry points are, the layers, the build/test toolchain, and the main risks to your feature (e.g. "this touches cron jobs and payments").

Step 2 — Trace the smallest end-to-end slice that resembles your feature (half day)
Don't start with your feature. Pick a neighboring one that already works and follow it from entry to persistence. Note the conventions along the way: how errors surface, how config is injected, how logging is done, how tests are written.
Evidence: An annotated trace — file → function → what it does — for that slice. A written list of "conventions I must follow" (not intuitions; things you observed in real code). A named shortlist of the 3–5 files you will actually touch. If you can't produce this trace, you're not ready to write code.

Step 3 — Spike the core path (day 2)
Build the ugly version: hardcoded values, no error handling, no tests. The purpose is to confirm the path you traced in step 2 is real and to surface what you didn't know you didn't know.
Evidence: A working spike demonstrating the feature's central data path, alongside a list of every assumption the spike broke and what you corrected. That correction list is the most valuable document in this whole plan.

Step 4 — Write the contract before the code (half of day 2 / day 3)
Once the spike proves the path, pin down what production needs: the inputs/outputs, the error cases, where it sits in the conventions from step 2. Then write the tests — they'll be red, but they're the specification.
Evidence: A one-to-two-page design doc, an agreed interface/API shape (with the team if there is one), and a red test suite that encodes intended behavior. If you can't write the contract without consulting the code, you haven't finished step 2.

Step 5 — Implement in small, verified increments (days 3–4)
Replace the spike with the real thing in small commits, each one keeping the suite green, leaning on the existing patterns. Run lint/tests/typecheck per commit — CI, not just locally — and exercise the actual path against a real instance (staging or a local environment that isn't stubbed).
Evidence: A branch with progressive commits, each green in CI; coverage on the new code; something that proves it works against reality (a test result, a log trace, a screenshot); and a review by at least one person who knows the codebase. The review counts as evidence — an unfamiliar codebase has tribal knowledge you cannot extract from the files alone.

Steps 6+ would be the things that actually make it "shipped": a migration plan and its rollback, feature flagging, observability, the release and post-release verification. But the first five get you to a reviewed, green, working slice in staging — which is the point at which you can say "this will work in production" with evidence behind it, instead of a guess.

生成耗时42.7s
输入 Token134
输出 Token2,354
token / 秒55.13
TTFT-

运行会以此提示词打开 AI Chat,需要登录并有积分。

模型详情

在 Playground、API 请求和内部工作流中使用相同的模型 key。

模型 ID
qwen3.8-flash
供应商
Qwen
协议
OpenAI Chat Completions
上下文窗口
1,000,000 Token
最大输出
131,072 Token
输入 Token
5.7143 credits / 1M Token
输出 Token
19.2857 credits / 1M Token
缓存读取
0.7143 credits / 1M Token
缓存写入
7.1429 credits / 1M Token

专为编程与长文本工作打造的高速 Qwen 模型

Qwen3.8 Flash 是阿里巴巴 Qwen3.8 系列的高速版本,专为编程、工具调用 Agent 以及无法在简短对话中容纳的长文档而设计。

大模型,低成本

总参数量达 1250 亿,每个 Token 仅激活约 60 亿参数。这也是它能保持超快响应且足够经济、轻松应对高并发任务的原因。

100 万 Token 上下文

单次请求即可放入超长规范文档、海量文件或完整的 Agent 运行轨迹。单次回复最长可达 131,072 个 Token。

支持图像与文本输入

模型不仅支持纯文本,还能理解屏幕截图、图表及各类文档。非常适合从屏幕画面开始的任务。

约 $0.057 / $0.193

每百万 Token 输入约 $0.057,输出约 $0.193,大约是官方公开定价的一半。缓存输入更便宜。上方价格栏显示的是实时费率。

Qwen3.8 Flash 的核心优势

根据 Qwen 随 2026 年 8 月版本发布的官方模型文档,Flash 在所对比的模型中,编程与工具调用能力表现最为优异。

代码库级任务

SWE-bench Pro 得分 62.5,SWE-bench Multilingual 得分 81.0。可用于定位 Bug、编辑多个文件并验证结果。

工具调用 Agent

DeepSWE 58.7,Toolathlon 73.5。能够稳定维持多步循环流程:分析失败原因、调用工具并重试。

代码与高难度问题

LiveCodeBench v6 为 91.9,GPQA Diamond 为 91.7。竞赛级编程与科学类难题皆能游刃有余。

屏幕视觉理解

OSWorld 部分得分 52.3;MathVision 得分 90.6(可运行代码时达 95.7)。可将屏幕截图和图表连同问题一起输入。

Flash 还是 Max?

管理 API 密钥 →

Flash 适合全天候持续运行;当任务难度远比预算更关键时,Max 则是旗舰之选。

01选择 Flash

适用于编程 Agent、测试与修复循环、长文档,以及任何注重预算成本的工作负载。1M 窗口支持完整涵盖超长轨迹,无需拆分。

02选择 Max

Qwen3.8 Max 是拥有 2.4 万亿参数的旗舰模型。当您需要最强性能的 Qwen 且 Token 成本居于次要时,请选择它。可在 /chat/qwen3-8-max 体验。

03相同的请求格式

两款模型均采用标准的 chat completion 请求格式。使用 Flash 时,将 model 设置为 qwen3.8-flash。当回答需要较长轨迹时,可调高 max_tokens(默认值为 8,192,上限为 131,072)。

常见疑问

01Qwen3.8 Flash 的用途是什么?

快速编程、工具调用智能体和长文档处理。它是更经济、更迅速的 Qwen3.8,而不是 Max 的简单缩小版。

02上下文长度是多少?

100 万 tokens。单次回复上限可达 131,072 个 tokens。

03费用是多少?

每百万 token 输入约 $0.057,输出约 $0.193,约为官方标价的一半。从缓存读取成本更低。每次工具调用不收取额外费用。价格栏显示的是实时费率。

04它能读取图像吗?

可以。截图、图表和文档图像与文本一样均受该模型原生支持。

05什么时候应该改用 Qwen3.8 Max?

当您需要旗舰级性能且愿意为每个 token 支付更高费用时。Max 是 2.4T 模型,而 Flash 则更适合大批量、高吞吐的调用场景。