早鳥價(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
README
輸入
限制回覆長度。推理模型也會計入思考內容。
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 請求與內部工作流程中使用相同的模型鍵。

模型 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,以及無法放入短對話的長文件所打造。

大模型,低成本

總參數達 1,250 億,每個 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 時,將模型設定為 qwen3.8-flash。當回答需要長篇輸出時,可調高 max tokens。預設為 8,192,上限為 131,072。

常見問題

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

快速撰寫程式碼、工具調用 Agent 以及長文件處理。它是更平價、更迅速的 Qwen3.8,而不是 Max 的縮小複製品。

02上下文長度是多少?

100 萬個 token。單次回覆最多可達 131,072 個 token。

03費用是多少?

每百萬 token 輸入約 $0.057 美元、輸出約 $0.193 美元,約為官方定價的一半。從快取讀取的費用更低。每次工具調用不收取額外費用。價格列顯示的是即時費率。

04它可以讀取圖片嗎?

可以。螢幕截圖、圖表與文件圖片都與文字一樣,為該模型支援的一部分。

05什麼時候該改用 Qwen3.8 Max?

當你需要旗艦級效能,且願意為每個 token 支付更多費用時。Max 是 2.4T 模型,而 Flash 則是專為高用量需求打造。